Configuration Syncs Overview
Configuration Syncs
Written by April Lockett
Updated at September 26th, 2023
There are two different types of data syncs associated with ClientTrack: Configuration Syncs and Replication Syncs1. This section will cover Configuration Syncs, a process that is initiated on demand.
Mechanically, a Configuration Sync (referred to as “Sync”) is the process of deleting all Forms, Workflows, Queries, etc., with an ID between 1000000000 and 1999999999 in the Destination environment and then copying any Forms, Workflows, Queries, etc., in that same ID range from the Source environment.
Not overwriting these items allows for a deleted element in the Source environment to be completely removed in the Destination environment after a Sync.
Most implementations will have two or three environments, but an implementation’s Production (PROD) environment will always play the role of the Destination environment when involved in a Sync. Syncs will normally take about thirty minutes but can take longer depending on an implementation’s database size.
The Destination database is backed up prior to the configuration changes being moved from the Source. The database backup remains in place for a period of 30 days to provide recoverability options to configuration changes for any unexpected behaviors encountered following the Sync process.
| 1 A Replication Sync is an automated process by which a production database is replicated to an Azure Advanced Analytics database, enabling analysis on production data by a client without interfering with production data or systems. While Replication Syncs are outside the scope of this document, they can be adversely affected by Configuration Syncs. |
