If you are performing a mass update of accounts or contacts, it is usually best to prevent the Salesforce connector from triggering the sync for all the records you are updating since it can cause a backlog to form. To prevent the connector from triggering the sync during these updates, you can set the "Celigo Update" field on the contact or account records you are updating. This field will only hold the value for the single update you are performing, so the next time you update the account/contact it will sync in its normal fashion.
Prevent an Update from Triggering the Account/Contact Sync
Comments
6 comments
Could you please clarify how to use this field? Do I check the checkbox to cause an update, or check the checkbox to prevent an update?
The article states, "To prevent the connector from triggering the sync during these updates, you can set the "Celigo Update" field on the contact or account records you are updating."
Set it to what? True? False?
Hi Peter Rozek,
Thanks for writing in and I apologize for the late response - I didn't see this comment coming in. I'm checking with the PM on this and he will update you asap.
Following. Also, if I already made the mass update, how do I see if there a backlog? Sometimes when reps change territories or through attrition, we need to mass update accounts to reassign reps. What is the best practice for doing this so that Netsuite and Salesforce don't get out of sync?
Hi Damon,
Being the Account and Contact Real-time flows (which trigger on any Edit and Save of the field update) the suggestion of setting "Celigo Update" to "true", helps in preventing the loop of record triggers to happen on ID write backfield Update and when Bidirectional flows are enabled (NetSuite Customer to Salesforce Account flow)
Mass Update will always update the Object in Salesforce and triggers the Integration flow to sync the data to NetSuite. Keeping the flows Account and Contact bidirectional enabled will always keep your data in sync in Salesforce and NetSuite.
Thank you
Setting the Celigo Update to 'true' seems counter intuitive. I would think if we are doing a mass update, which I didn't realize wasn't supported by Celigo, we'd want to set Celigo Update to 'false'. How many records can Celigo handle? It seems there are lots of cases where even users can 'inline' edit up to 250 records at time. Does this mean those changes won't sync either? Or just that a backlog will occur and it will take a bit longer for those changes to be reflected?
Hi Damon,
Celigo won't have any limit in syncing the records updated via Mass update or Inline Edit, being the flow Real-time, the integration flow is smart enough in handling the data and will take care of syncing the records updated.
Please feel free to reach us, if you're seeing any issues in syncing the records via mass update.
Thank you
Please sign in to leave a comment.