Salesforce System Updates
Why are historical records being imported in mass into Ambition?
In order to keep Ambition's data as up to date as possible, records from Salesforce are imported into Ambition based on updates to a record's 'SystemModstamp'.
From Salesforce's documentation: 'SystemModstamp' is the date and time when a record was last modified by a User or by an automated process (such as a trigger.) In this context, 'trigger' refers to Salesforce code that runs to implement standard functionality, rather than an 'Apex trigger.'
Since automated processes will update a record's SystemModstamp, those updates will then signal to Ambition that there is an update on the record and that those updated records should be imported into Ambition.
My organization is constantly running automated processed in Salesforce. Is there another date field we can use to keep Ambition data up to date?
While 'SystemModstamp' is the date and time that will reflect when a record was last modified by a User or by an automated process (such as a trigger), 'LastModifiedDate' will reflect the date and time when a record was last modified by a User.
If system updates to Salesforce records is impacting how real-time your data appears in Ambition, it may be appropriate for your organization to use 'LastModifiedDate' as the signal for Ambition to rely on for recognizing when records have been updated. The change can be made on an Object by Object basis if there is a particular Salesforce Object that is frequently being impacted by automated processes.
Salesforce's help documentation outlines when 'LastModifiedDate' and 'SystemModstamp' will differ.
If you think it's appropriate for your organization to use 'LastModifiedDate' instead of 'SystemModstamp', reach out to firstname.lastname@example.org.