do_sync_flag

do_sync_flag explains various synchronization statuses between Source and Database and helps in database-to-source Replication.

do_sync_flag helps update existing data and insert new data into Salesforce. The value of do_sync_flag & the description is shown in the below table.

Value	Description
Y	When Salesforce to Database replication is successfully completed, do_sync_flag for all the records in the database will be ‘Y’
S	If the data is edited/updated in database, it is required to edit / update the same in Salesforce too. To do this do_sync_flag value must be changed to ‘S’
D	If the data is deleted in Salesforce after replication (Source to DB), when the replication (Source to DB) is run for the next time, the do_sync_flag value changes to ‘D’.
X	If the data needs to be purged in salesforce after replication (DB to Source ), the do_sync_flag value needs to be changed to "X"
F	When Salesforce to Database replication is not completed successfully, the do_sync_flag for all the records in the database will be ‘F’
B	When the do_sync_flag is set to "B," it will block data from being transformed/ Updated on the database if any changes are made on the source and the source to db command is run

• When Salesforce to Database replication is successfully completed, do_sync_flag for all the records in the database will be ‘Y’.

• To do this, the do_sync_flag value must be changed to ‘S’ along with the necessary changes to the records in the database.If the data is edited/updated in the database, it is also required to edit/update the same in Salesforce. To do this, the do_sync_flag value must be changed to ‘S’ along with the necessary changes to the records in the database. After the replication (DB to Source) all these changes will reflect in Salesforce. Example: Account sForce in Salesforce does not have Type, which is already replicated in the database. If the type is updated as ‘Customer – Channel’ in the database, Salesforce must also be updated. In order to update in Salesforce, the do_sync_flag value must be changed to ‘S’, which must be saved before running the replication DB to Source. After successful run, Account sForce will have Type ‘Customer - Channel’

  1. Account sForce does not have Type in Salesforce

  

  1. After replication (SF to DB), do_sync_flag value for sForce Account is ‘Y’ and sfType is ‘NULL’.

  2. sfType for sForce is manually updated as ‘Customer – Channel’ in database and then do_sync_flag is manually updated as ‘S’.

  3. After running Replication (DB to Source), sForce Account in Salesforce is updated with the Type ‘Customer – Channel’.

• If the data is deleted in Salesforce after replication (Source to DB), when the replication (Source to DB) is run for the next time, do_sync_flag value changes to ‘D’. Example: Account ‘Pyramid Construction Inc.’ is deleted in Salesforce which is already replicated in database. Account Pyramid Construction Inc. data is already available in database with do_sync_flag value ‘Y’. When the Source to DB replication is done for the next time, do_sync_flag value changes to ‘D’ by itself. This signifies that Account ‘Pyramid Construction Inc.’ does not exist in Salesforce

  1. After Replication (Source to DB), do_sync_flag value is ‘Y’ for the account ‘Pyramid Construction Inc.’

  2. Account ‘Pyramid Construction Inc.’ is deleted in Salesforce.

  3. After Replication (Source to DB), do_sync_flag value changes to ‘D’.