Tag: Database
Resetting the Supervisor Password in a Local Creatio System
If you have a local Creatio installation, with access to the database, you can easily reset the Supervisor password using a SQL statement. User passwords are encrypted in the database and the user's Id is used as a seed for the encryption. With that in mind, each user's Id is different, so the below statement will not work for...
Troubleshooting Constraint Violation Errors in Creatio
If you're experiencing constraint violation errors when debugging code or processes in Creatio, it can sometimes be difficult to understand where exactly the problem lies. This article will outline how to troubleshoot these types of errors.
Background
In Creatio, when you add a lookup to an entity object, it adds a database-level constraint that enforces that values put in the lookup...
Set Up a Database Connection in Infor CRM
In order to connect Infor CRM software to the database, you must set set up the Data Link in Connection Manager; and set up the connection to the Data Link in Data Link Manager.
Sysdba SQL login for Infor CRM Database
In order to prepare a SQL server to run Infor CRM, you must set up a SQL login for CRM to use, and must link it with the sysdba user in the CRM database.
Moving or Restoring Databases in Infor CRM (formerly Saleslogix)
Use the sa SQL account to move or restore CRM databases, but use sysdba to connect to them.
SQL Function for Creating Pretty Key Values for Data in Infor CRM
Some entities in Infor CRM (Saleslogix), such as Tickets, use a “pretty key” as an easier to use value to reference the record. These pretty keys take a table ID value and then create a value like 000-00-001234. If you are creating an external application with this functionality, you’ll need to be able to create these pretty keys there...
SQL Stored Procedure to Create SalesLogix Table ID Values
Most of the SalesLogix systems I see now days no longer use remote users. Instead, all users VPN into a central network to access SalesLogix, or use the SalesLogix Web and Mobile clients instead for remote users. This removes the need to worry about things like synchronization for remote users and also allows you to do some SalesLogix table manipulation without going through the SalesLogix OLE DB Provider since things no longer have to be "sync aware". This post will provide you with a SQL Stored Procedure to create SalesLogix table ID values from inside of SQL scripts. Keep in mind, you should only use this if you do not have remote users that synchronize with the host system.
Flattening Out SalesLogix Data To Combine Multiple Rows into a Single String using SQL
A question came up from a person attending our current Report Writing class about how to flatten out data that exists as multiple rows in the database to a single string in a report. There is a really cool trick you can do in SQL to accomplish this which I previously outlined in a post on my personal blog where I outline a technique that can be used to make a query append each value from the rows in the query to a variable. Without using cursors, you will end up with a variable that has the values appended to it as one single string which can easily be used in reporting.
Fixing the Orphaned SYSDBA SQL User
Ok, I see in my logs constantly google searches for “fixing the sysdba user“ that lead to this blog. This is a common thing I find in my logs, but strangely enough, I've never posted anything about fixing the sysdba user. So, drumroll...
sp_change_users_login 'Update_One', 'sysdba', 'sysdba'
Ta-da! For people who work with SalesLogix often, this is something well known. However this...
