CT-809: Row version

[Karen_Mendez2]

Hi team,

We are experiencing the following error in our Azure Synapse Link for Dataverse:

CT-809: Row version change tracking property disabled in Table. This table is paused. Visit aka.ms/SynapseLinkErrors to fix

The error doesn't point to a specific table, but several FnO tables that were syncing correctly are now showing errors. This started happening suddenly, and I'm trying to understand:

• What exactly causes the FnO-809 error?

• Could it be related to a recent database refresh or restore in our UAT environment?

• How can I resolve this error and re-enable the affected tables?

• Is there a way to prevent this from happening again in future environment refreshes?

Any guidance or shared experience would be really appreciated.

[v-mdharahman · Accepted solution]

Hi @Karen_Mendez2,

Thanks for reaching out to the Microsoft fabric community forum.

Thanks for raising this issue. The CT-809 error you're encountering in Azure Synapse Link for Dataverse is caused by the row version change tracking property being disabled for one or more tables in your Finance and Operations (FnO) environment. This typically happens after a database refresh or restore, especially in UAT environments. During such operations, certain configuration keys including the one required for change tracking can get reset or disabled.

To resolve this:

* Re-enable the configuration key for row version change tracking in your FnO environment. You can do this via the System administration > Setup > Azure Synapse Link configuration settings. Ensure the key named enable row version change tracking is turned ON.

* Remove and re-add the affected tables to your Synapse Link profile. This will reinitialize the tables and resume syncing. Also you will nott lose historical data, but the tables will be re-synced from scratch.

* Also verify the environment is not in Admin Mode: If your Power Platform environment is in Administration Mode, all services including Synapse Link are paused. So disable Admin Mode and ensure Background Operations are enabled.

To prevent this from happening in future refreshes always verify and re-enable the configuration key post-refresh. ALso consider automating this check as part of your post-refresh validation steps.

You can find more details in the official troubleshooting guide here: Azure Synapse Link for Dataverse trouble shooting guide - Power Apps | Microsoft Learn

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.

[ManovBGS]

Hello there,

Can you please explain where exactly this menu is: System administration > Setup > Azure Synapse Link configuration settings. I am not able to locate this in Finance and Operations...