Merging duplicate Salesforce Accounts but leaving Celigo sync enabled
Hello, we have the Salesforce Account and NetSuite Customer syncs in place but have found some data that needs cleaning. I understand that we can either break the Celigo sync before cleaning the data, or keep the sync in place while cleaning the data. This seems to be an issue of how much risk we are willing to accept. Has anyone successfully merged duplicate Salesforce Accounts without breaking the Celigo sync in a production environment?
Regards
Steven Paice
-
Hi Steven Paice,
Did you put in a support ticket on this?
0 -
Steven,
What did you end up doing? We are in a similar situation, needing to merge some duplicate customers and contacts, and I haven't found any helpful documention on how to be successful.
Thanks,
Kenneth
0 -
Hi Kenneth,
Merging the duplicate Salesforce Accounts in Salesforce is considered as an update on Salesforce Account if the Celigo Salesforce Account to NetSuite Customer Add/Update flow is enabled, being it the Real-time flow, all the updated or merged accounts will be considered for data sync to NetSuite and trigger the flow.
The Celigo Integration App SFNSIO is smart enough to submit the huge data to IO for sync, it won't lead to break or downtime of IA.
If you don't want to sync all the merged account updates in Salesforce to NetSuite, you can configure the Qualification criteria on the Flow set to send only specific records which meet the criteria.
Please feel free to correct me if I'm wrong in understanding the question.
Thank you
0 -
Nithin,
Thank you - you have understood my question, and that is a very useful answer.
Will you clarify 2 things:
1) when I merge in SF (or in NS) the 'duplicate' records are deleted leaving only the 'master'. Does that deletion sync via Celigo, or do I need to delete the 'duplicates' manually in the other system?
2) If I didn't want to sync merged account updates, what fields might you suggest I use in the Qualification criteria? I am having a hard time seeing a scenario where I would not want to sync.
Thank you again,
Kenneth
0 -
Hello Kenneth,
1) when I merge in SF (or in NS) the 'duplicate' records are deleted leaving only the 'master'. Does that deletion sync via Celigo, or do I need to delete the 'duplicates' manually in the other system?
A) Currently IA flows only support the creation and updating of records via Integration, deletion of records is not support.
We need to manually delete the duplicate records in the other system, my suggestion would be to use a saved search to identify the duplicate records and perform the mass delete.
2) If I didn't want to sync merged account updates, what fields might you suggest I use in the Qualification criteria? I am having a hard time seeing a scenario where I would not want to sync.
A) You can select any field, which is unique on the updated Customer record after Merge, My suggestion would be to set the criteria based Last modified date or time if you are performing a merge of accounts at a time.
Example :
Still, this will depend on the fields which are getting updated after the merge of records.
I hope this will help you to sync the required data.
Please feel free to reach out to Celigo support for any help.
Thank you
0
Please sign in to leave a comment.
Comments
5 comments