Manually Updated Salesforce Values Aren't Reflected in the Destination

After manually updating some values in Salesforce, you may find that the values in the destination don't reflect the changes. Find out what may cause us to miss an update and how to ensure your data is up-to-date.

Why are some updates missed during syncs?

To detect changes and additions in your Salesforce data, we monitor the following timestamp fields within Salesforce's API responses:

• SystemModStamp
• LastModifiedDate
• CreatedDate
• LoginTime

If a change does not update any of these fields, Fivetran is unable to detect and sync it. To ensure your destination reflects the most recent data, you must manually re-sync each affected table.

Common scenarios that may result in missed data

• Manual updates that don't affect timestamp fields: Some manual updates in Salesforce may not update the fields we monitor, preventing these changes from syncing to your destination.
• New columns added to existing records: When you add a new column in Salesforce, incremental timestamp fields for existing records are not updated. As a result, we are unable to sync older records for the new columns during incremental syncs.
• Salesforce operations that don't update timestamp fields: Some Salesforce operations may update records without modifying incremental timestamp fields.

How to manually re-sync a Salesforce table

To manually re-sync tables containing out-of-date values, do the following:

1. In your Fivetran dashboard, go to your Salesforce connector page.
2. In the top right corner, pause the connector by setting the ENABLED toggle to OFF.
3. Select the Schema tab.
4. Locate and hover over the affected table.
5. On the right side of the screen, click Re-sync.
6. In the confirmation pop-up window, click Start re-sync.
7. Repeat steps 4 through 6 for each affected table.
8. Unpause the connector by setting the ENABLED toggle to ON.