Applies to Product - Dynamics 365 Supply Chain Management
What’s happening?
Customers have reported that certain actions in the Finance and Operations environment, such as database exports and backup/restore operations, can stop the syncing of the Fabric Synapse Link. Additionally, after performing a database refresh, some tables in the Synapse Link may show outdated information despite the sync status appearing active.
Reason:
The database refresh operations disable both types of change tracking on tables/entities: - SQL CT Change Tracking (utilized by DIXF) - SQL Row Version Change Tracking (utilized by Synapse sync)
Resolution:
- A resync is required for the Synapse Link after every Finance and Operations database refresh.
- Change tracking must be re-enabled via one of the following options:
- Disable and re-add the virtual entity in Dataverse.
- Unlink and re-link the entity if it was synced via Synapse Sync.
- If the Synapse Link stops working after a backup and restore operation, the Azure Synapse Link for Dataverse profiles are not included in the environment backup. Users should use solutions to transport the link across environments.
- To preserve the configuration of the Azure Synapse Link across environments, export and import the configuration after restoring the environment.
- For further assistance, refer to the documentation on managing Azure Synapse Link with Environment Events and troubleshooting common issues.