Views:

Applies to Product -Dynamics 365 Lifecycle Services


What’s happening?
Customers are experiencing synchronization errors when attempting to sync standard tables, resulting in messages indicating that the initial sync is in progress or that there are indexing errors.


Reason:
The underlying cause of the synchronization issues is related to the row version change tracking property being disabled in the affected tables. This can lead to tables being paused with error messages during the synchronization process.


Resolution:

  1. Ensure that the configuration key SysDeletedObjectSysRowVersion is enabled. This key is necessary for the SQL row version change tracking functionality to work correctly.
  2. If SysDeletedObjectSysRowVersion is enabled by default, it might be causing a conflict. Disable it and enable the appropriate configuration key.
  3. Verify that the ‘Allow Row Version Change Tracking’ property is set to Yes for the tables in question. This property must be enabled for the SysRowVersion field to appear and function correctly.
  4. Ensure that the SysRowVersion field is correctly added to the tables. This field should be of the extended data type SysRowVersion.
  5. After verifying all these changes, restart the IIS (Internet Information Services) to apply the changes.
  6. Once the above steps are completed, check if the tables are now visible in the Synapse link.
If the issue persists after following these steps, further investigation may be required.