The Incremental load type requires that each table have a primary key and a timestamp that is updated each time a change is made to a record. If your endpoint does not have a column or field to store the last updated timestamp, you will need to add one. Make sure that the column is not nullable, contains no null values, and updates the timestamp for all changes. If you can't add a timestamp, you can use Full load instead of Incremental.

For the last updated timestamp, AutoSync supports values up to nanoseconds. The MySQL destination endpoint is an exception because it doesn't support fractional seconds.

Deletions are not synchronized. However, for Salesforce, you can configure AutoSync to track deletions.

Important: Some Salesforce objects do not have a LastModifiedDate field because they are not updated after creation. For incremental loads in this case, AutoSync recognizes new records from their CreatedDate field and loads them to the destination.

The Incremental load type is supported for: Marketo, Microsoft Dynamics 365 for Sales, Oracle, MySQL, Salesforce, ServiceNow, and SQL Server sources when synchronizing to Azure Synapse, Google BigQuery, Oracle, SQL Server, and Snowflake targets.