Tips and Tricks from R.J., the SalesLogix Consultant

Working in SalesLogix CRM on a Solid Platform

Tweet

 

Data in SalesLogix CRM can change, sometimes leaving a user in a state of flux.

A Few Classic "Trouble" Areas

1. Account Ownership and visibility for New Accounts. You diligently enter in new account and contact information, even being nice to your admin and entering in a LeadSource, the correct Team, a complete Address, and the Mobile Phone for the contact. Then you click OK/Save and the account disappears! This started cropping up in my first SLX installation 15 years ago in February, 1997.
   
   What happened? The user filled in the correct Team/Owner for the new account, except and they (the user) weren’t a member of that team. So when they looked through Groups, Lookups, back arrow to the account, etc., it was never found. The punch-line? They entered in the account information again, creating a duplicate. Ouch.
    
2. My group’s "current" record changed! Or my group no longer has the same records in it?! If you have a field in the group Conditions or Sort tabs that will change as you work on the view, what did you expect? You have a group that’s based on Status = "Active" and you change the Status value to "Aardvark." When the group is refreshed, that record won’t be in the group anymore! Or you are sorting the group based on the ModifyDate field, when you change a field value and hit the Save icon. SalesLogix automagically changes the Modify User and Modify Date fields to the Current User, time-stamped to Now. The screen is refreshed and the group has changed, additionally, where you are in the group has changed.
    
3. The opportunity is "Closed," but now it isn’t? I’ve had users working on the same record at the same time as someone else (or even better, logged in as themselves in two different sessions of SalesLogix). Whatever is the last changed value will store to SalesLogix, so it’s best to keep everyone else off of the record - including yourself - that you are working on. From a workflow perspective, you may need to look at the database record to see if it has changed prior to saving the data. This requires some complex scripting to get rid of the concurrent access to a single SalesLogix record.

Bottom Line: Don’t change horses in the middle of a stream.