8/18/2025 6:27:45 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 writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
Merging accounts
Posted: 19 Nov 07 4:55 PM
|
Hi guys,
Am not sure if this is the right forum to post it but I didn't anything else that this questions should go to. Anyway, my users are complaining that when they merged some accounts the Primary account didn't have some information that was supposed to come from the Merge account. The weird thing is that only certain services within the merge account don't get moved to the Primary account.
However, when I tried merging some accounts in my development environment - it worked flawlessly (the merged accountid was replaced by the primary accountid). So, I couldn't pinpoint the problem.
Does anyone have experienced this before or do you think the user might have done something wrong?
Thanks in advance. |
|
|
|
Re: Merging accounts
Posted: 20 Nov 07 9:55 AM
|
Usually when users complain about something mysterious and not very likely, I ask them to let me know when they perform that certain task so I can watch. After a couple of times, I think the users realize it's just a "ghost" and it went away. I think around here I am known as the excorcist of SalesLogix 
Something I guess you could try is to look directly at the database and see if there are any orphaned records. If they didn't get moved over in the merge, they would still be associated to an account that wasn't there. As far as I know, merge does not delete any One-to-Many records - it only overwrites fields on the One-to-One level.
One last thing you could try is to track your merges by hijacking the merge code in the Main Views. There was a thread on this maybe a month ago that I started on this task. Then, when you are tracking the merge, you could record the number of records from the table that the user claims loses records, and when the users complain of the issue again, you can go back and look at the merge record and say, "There were only that many to begin with. I record how many records were there before the merge." Then you can have your proof  |
|
|
|
Re: Merging accounts
Posted: 21 Nov 07 3:31 AM
|
Hi,
We do understand your frustrations with the standard SalesLogix merge funciton, thats why we build our Paribus product and the Paribus for SalesLogix plugin component.
Paribus is our intelligent data matching technology which enables you to match SalesLogix (and other systems) data such as Accounts and Contacts for the purposes of duplicate identification.
Once you have matched your Accounts and/or Contacts, the Paribus for SalesLogix plugin component will enable you to due diligently merge "100%" of the data (including all one to one data, one to many, and all custom data).
Furthermore the plugin also manages the complexities of data merging for remote database sync cycles. Catering for remote data coming in post the initial merge and then performing a second merge to prevent orphan records occurring.
My apologies for the shameless product plug here, however if this is perhaps of interest to you, then please let us know. You may wish to view the following links for more information:-
http://www.qgate.co.uk/paribus.html
http://www.slxdeveloper.com/forum.aspx?forumid=6000&postid=4267
Regards Mark Cooper Director for Product Engineering QGate Software |
|
|
|
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!
|
|
|
|
|
|
|
|