The info in this doc only applies to database integrations.
There may be times when you need to fully replicate a table (or tables) that usually update incrementally. If, for example, you add a new column and want to backfill data for already-replicated rows, forcing a full re-sync of the table will populate the column for existing rows and replicate new records.
You can do this by resetting Replication Keys. Replication Keys are columns that Stitch uses during the replication process to identify new and updated data. For detailed info on how Replication Keys work, check out the Selecting Replication Keys doc.
Here's what we'll cover:
Resetting Replication Keys can be done at the integration or table level.
Before you reset the Replication Keys for your table or integration, consider the following:
If you have questions or concerns about resetting Replication Keys, we encourage you to reach out to support before proceeding.
Resetting Replication Keys at the integration level will clear the saved values for all tables in an integration AND queue a full re-sync. This can't be undone.
Resetting Replication Keys at the table level will clear the saved values AND queue a full re-sync for that table. This can't be undone.