6/30/2025 4:28:33 AM
|
|
slxdeveloper.com Community Forums |
|
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
Salesprocesses
Posted: 28 May 10 8:11 AM
|
Hi all
We have recently upgraded from 7.2 to 7.5 and we are running both Lan and Web clients.
After searching through the plugins table for salesprocesses we have noticed that they have been duplicated, the only difference is the created by user. The first user is Admin and the second is SYST00000001. After testing creating an opportuninty through the web client I noticed it used the SYST user salesprocess even though it has not been released.
Would I be right in assuming that the one created by Admin is for the Lan users and the other is for the web users? or should they both be using the same one?
Regards Andrew James |
|
|
|
Re: Salesprocesses
Posted: 28 May 10 8:31 AM
|
You have just discovered SalesLogix releases.
When a user creates an Item that is stored on the Plugin table (Mail Merge Template, Group, Sales Process), it creates a record with the USERID of the Creator. Only the user who created it would use it.
Then, if that user Shares it (Releases it), then a copy is created for each person (or team) that it is released to.
Now, what sometimes happens is that, after releasing it, the creator goes back to the original and makes changes, in that case the "Released" copies will be different until a new Release is initiated.
SYST0000001 is the ID for the Everyone system Owner, and all users have access to it. When you release items to, a user may have overlapping copies of it (e.g. you release a Sales Process to 2 teams, but a given user belongs to both teams). In that case, which entry is used is undefined. Similar to when the Owner releases it in such a way that he/she also ends up having access to the Copy of the plugin (although I believe in that case it will use the Release copy rather than the Original copy as you found out).
Also, there are cases when plugin releases get "corrupted". When you look at the Plugin table, there is a field called "BASEDON" which contains the ID of the Original Plugin. There are cases when the original plugin may have been deleted, but the copies didn't. Since the list of SPs generated is not based on IDs, it may indeed pull in a copy of a plugin that is orphaned (although by name it matches a new Plugin).
In this case, I would suggest you look at the BASEDON field, and determine if indeed this is a release or just an orphan record (in which case you would be safe to delete). |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|