Source Control with Salesforce

When reading data from Salesforce.com, it is recommended to use SystemModStamp as a source control field. Via a source control field, you have full control over the data that is being transferred to the destination system and the overall performance is improved by using this system field. SystemModStamp is strictly read-only. Not only is it updated when a user updates the record, but also when automated system processes update the record.

1. In order to use it on your integration, you simply need to go to your transfer and click on the Edit pencil icon on the transfer section called " Source Control".
2. Next, add the field SystemModStamp in the field called "Source Control Field" and then Save it.

Note: Don't forget to click on Activate Changes whenever you make any change on your transfer. This will allow the transfer to be updated correctly.

There might be situations when SystemModStamp may not be available for the object you’re querying against. You also may want to consider alternative approaches that would address other scalability concerns together. Here are some options that will help you optimize performance and scalability of your queries:

1. Use the system field LastModifiedDate in certain scenarios (it is automatically updated whenever a user creates or updates the record and there will always be a difference in stored values between SystemModStamp and LastModifiedDate because ‘LastModifiedDate <= SystemModStamp’ but never ‘LastModifiedDate > SystemModStamp’.)
2. Use a custom date field and use workflow field updates or triggers to copy the value stored in the system fields that are available. And, of course, it has to be indexed.
3. Add a skinny table: If you have performance issues due to large data volume, consider adding a skinny table. Skinny tables include indexed LastModifiedDate by default.