Do not enable No Count on a SQL server running Infor CRM (Saleslogix).
I recently bumped into an issue with the order in which the utility (CreateUnicodeDB) creates database objects. SQL Users and schemas are processed first, followed by SQL tables, followed by the other SQL objects. In this particular database, there were scalar UDFs being used to create computed columns in a number of the SQL tables. Since the utility creates Tables before UDFs, it would error out on any table referencing that non-existent U...
It is possible to hide groups at the database level, thus speeding up load times.
When creating a report in Infor CRM (Saleslogix) that filters based on date, the options can be a bit tricky. Luckily, most of tables and columns in the underlying SQL database are named fairly intuitively.
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 […]
There are simple SQL statements that can be used to delete or change a single piece of data in Infor CRM (Saleslogix).
When we are assisting clients with an upgrade or new installation of CRM, we are frequently asked what version of SQL should be used.
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 "s...
I had a request to post on how you could replace characters within a blob field in the SalesLogix database. Blob fields are database fields that hold any sort of binary information (such as text, images, audio, etc..), but SalesLogix uses them primarily for holding large amounts of text, since you don't have to define a field length. The LongNotes field in the History table is a good example.
I previously posted about using an update trigger to enforce data rules in SalesLogix. Since I was working on another trigger now, I also wanted to post a simple example of an Insert Trigger.
If you've ever created a SSIS package and wanted to provide a way for end users to run that package without having to run the Business Intelligence Development studio, you can compile the package into a dtsx file for them to run. This would require them to manually alter connections and variables, which can get complicated for an average end user. Alternatively, it is pretty simple to put together an application which can be used to run the ...
Using pivot queries in SQL is a great tool for rotating data, but what if you need to do something more complicated with multiple data sources and multiple columns? Recently, I had a request to pivot some data from multiple similar tables and to rotate that data into a columnar format.
I am four posts into building a drill down report using Sage SalesLogix Visual Analyzer and Dashboard as a my guide. This series of post starts with a post labeled “Updating the Managed Quota Area for Sage SalesLogix” , if you follow the links on each post you will eventually end up back on this post. In the last […]
Over the last three posts we have updated the Quota’s are of Sage SalesLogix, we have built SQL views to collect both the Quota data and the Actual Numbers for comparison. Now we will start writing our report. I am not going into to much detail on layout. My goal is to walk you through the common steps: connecting to the […]
I have just started writing a series of posts that will lead the reader of this blog through the creation of a report with the same kind of data break down as you see in the standard Sage SalesLogix Visual Analyzer and the Sage SalesLogix Dash Board. In the first week I provided a method to effectively establishing quotas […]
If you read last weeks post, you will know I am setting up to build a user based report that will give the reader a lot of the same data you see in the standard Sage SalesLogix Visual Analyzer and the Sage SalesLogix Dash Board. Last week I provided you the ability to effectively set goals for your users by […]
I've previously posed about a number of useful functions available to you within the SLX_Common script in the LAN version of SalesLogix. I'd like to go a little further in-depth about a couple of functions which are helpful for creating new SQL Query strings. In a recent project, I needed to build a query interface similar to what you find in standard opportunity products view. The SLX_Common script holds a couple of functions that I ...
The SLX_Common script included in SalesLogix contains a number of simple, yet useful, functions that you can use within your own functionality to save yourself some time by not having to reinvent the wheel each time you need some simple functionality.
In a recent project, I had to create a SQL Server Integration Services package to basically copy contact information (which was being stored in the Account.Account field) from the Account table into the Contact table. Since the Contact name was being stored in it's entirety within the account field, I needed a way to parse the Contact information to populate the individual contact name fields in the contact table.
A couple of weeks ago, I posted about using User Defined functions and Cross Apply to parse data in SQL server. The second part of the import I was working on required me to take that parsed data, perform some manipulations, and then recombine that data. Surprisingly, I found that putting that data together was much more difficult then pulling it apart in the first place. After much experimentation, this is what I came up with...