Three configurations in ClientTrack Sync conditionally depending on the environment they were created in:

1.  The Codes Table

The Codes table (not to be confused with Evaluation Codes) will Sync, including each Codes' OrgGroupID.

If you create a Code in the Source environment marked as "All Organizations", it saves in the OrgGroupID table with the value of "-1" and will Sync as expected.

If Users only have specific Organizations selected to have access to a specific Code, after the Syn, the Code will not retain those Organization Access configurations due to the OrgGroupIDs being associated with different values in different environments.

If a User needs to have a Code be accessed by specific Organizations, create it in the Destination environment only or change the configurations post-Sync. Records in the Codes table that had been created in the Destination environment will not be removed by a Sync.

2.  Eligibility Rule Sets

3.  Queries designed in ClientTrack Query Designer

If the query logic is no longer valid due to changes in your database schema the sync process will communicate a warning to the Engineer conducting the sync. The Engineer will communicate any queries that are no longer valid at the close of the configuration sync. The query will still be visible within ClientTrack but will not query against the database until the query logic has been updated.

A similar process is happening with the tables associated with Query Designer and the Eligibility Rule-Sets. When a User creates a Query in the Production (PROD) environment, those Queries will all start with a 2000000000 number and because it is not in initial Sync ID number range, will be left alone during a Sync.