topic Re: Dynamics 365 F&O to Fabric Integration(change tracking disabled) in Pipelines

Dynamics 365 F&O to Fabric Integration(change tracking disabled)

Anonymous — Thu, 24 Oct 2024 07:42:21 GMT

Hi Community,

We have a requirement where we need to bring Dynamics F&O tables/entities to Microsoft Fabric (to which the change tracking is not enabled). I am trying to figure out a solution as it is on high priority.

Please let me know if there is any workarounds like Data pipelines/ Dataflows (Using OData and Dataverse but I am unable to see non CDC tables).

Additionally, I would like to understand if the tables or entities need to have change tracking enabled(or ay specific conditions) in D365 F&O in order for the tables/entities to be reflected in PowerApps/Dataverse.(Apologies as I am new to Dynamics/dataverse).

Thanks in advance!

Re: Dynamics 365 F&O to Fabric Integration(change tracking disabled)

FabianSchut — Thu, 24 Oct 2024 13:33:55 GMT

Hi Anonymous, according to documentation, track changes need to be enabled indeed: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entities-portal?tabs=excel

Track changes

Enables data synchronization in a performant way by detecting what data has changed since the data was initially extracted or last synchronized. This option must be enabled for certain features such as Azure Synapse Link for Dataverse

Re: Dynamics 365 F&O to Fabric Integration(change tracking disabled)

Anonymous — Fri, 25 Oct 2024 04:17:00 GMT

Hi FabianSchut ,

Thanks for the response.

However, I am assuming when we connect using OData in Data Factory Pipelines/Dataflows Gen2, we don't require Azure Synapse Link for Dataverse.

Please let me know if there are any work arounds to achieve non-cdc tables to Fabric. Is it possible to achieve this? as i don't find any documentation specifically mentioned on Data factory related pre-requisites.

Thanks again!

Re: Dynamics 365 F&O to Fabric Integration(change tracking disabled)

Anonymous — Mon, 25 Nov 2024 05:11:38 GMT

Hi Community,

As per the latest communications with support, it is confirmed that non-cdc tables cannot be brought as part of the best practices. The alternate option is
1. Enable change tracking as FabianSchut mentioned, if the option is not available then either Microsoft needs to enable in the backend or
2. Create a custom entity and enable change tracking.

Thanks and happy learning!