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...
Recently, I worked on an import where I spent a considerable amount of time working out how to effectively parse data from a SQL table, for insertion into another table.
In a recent project, I used triggers to enforce some data rules in the Ticket area of SalesLogix. We did this because our client was using both the LAN as well as the Web clients. We were having some difficulty seeing changes in the LAN client when values were set in the Web, and vice-versa.
There are many ways to get your data into a Microsoft Excel spread sheet for reporting purposes. Business Objects Crystal and Sage SalesLogix both offer an option to kick out report data to an Excel spread sheet. Last week I worked with a client who wanted exactly that, a set of data exported to Excel […]
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,...
I wrote about this topic just prior to The Crystal Report Writing class. During the class the question was asked "What about using the Execute SQL tool in the SalesLogix Administrator for syncing out SQL views to remotes?" As a development team we have looked at this before and always found that it just did not work. But we had not tested it in quite a while so we decided to try it again, and this time it worked.
The scenario is you have created a SQL view for use in a Crystal Report. Your end users are excited about the report but then you started getting phone calls from your remote users that the report will not run. You realize that the view you used to help organize your data did not synchronize […]
Did you know that you can include SQL views in SalesLogix? This can be a very handy method to include data that is not normally part of SalesLogix. It is important to note, that these changes are not sync-aware. However if you are running SalesLogix LAN in a network only environment, this can be a helpful way to include data from external sources.
Picklists in SalesLogix are a very useful tool, but did you know you could also you values from an existing picklist to populate other list-based controls such as ComboBoxes, CheckListBoxes, ListViews... even Radio groups? You simply need an understanding of the structure of picklists in SalesLogix: