Applies to Product - Dynamics 365 Supply Chain Management
What’s happening?
Customers are experiencing an issue where Finance and Operation tables are not populating when configuring the Synapse integration, with only Dataverse tables appearing.
Reason:
The underlying cause of this may relate to several factors, including: - Change tracking not being enabled for the Finance and Operation tables. - The environment being in Administration mode. - Insufficient permissions for the user attempting to configure the integration. - Networking misconfigurations between Azure resources. - The Synapse workspace, storage account, and Power Apps environment not being in the same geography.
The underlying cause of this may relate to several factors, including: - Change tracking not being enabled for the Finance and Operation tables. - The environment being in Administration mode. - Insufficient permissions for the user attempting to configure the integration. - Networking misconfigurations between Azure resources. - The Synapse workspace, storage account, and Power Apps environment not being in the same geography.
Resolution:
To resolve this, the following steps should be taken: 1. Create a Spark Pool: Follow the documentation to create a Spark pool for the Synapse integration. Refer to the documentation titled "Choose finance and operations data in Azure Synapse for Dataverse - Power Apps" for detailed instructions. 2. Enable Change Tracking: Ensure that change tracking is enabled for the Finance and Operation tables you wish to export. 3. Disable Administration Mode: If the environment is in Administration mode, disable it by accessing the Power Platform Admin Center and toggling the Administration mode off. 4. Check Permissions: Verify that the user has the necessary permissions, including: - Dataverse System Administrator role. - Synapse Administrator role if linking with a Synapse Workspace. - Reader role access to the resource group containing the storage account and Synapse workspace. - Owner and Storage Blob Data Contributor role access for the Azure Data Storage. 5. Networking Configuration: Ensure that public network access is enabled for the linked storage account and that all IP addresses are allowed if linking to a Synapse Workspace. 6. Geography Check: Confirm that the Synapse workspace, storage account, and Power Apps environment are all created in the same geography.
If the issue persists after following these steps, further investigation may be required to identify additional underlying causes.
To resolve this, the following steps should be taken: 1. Create a Spark Pool: Follow the documentation to create a Spark pool for the Synapse integration. Refer to the documentation titled "Choose finance and operations data in Azure Synapse for Dataverse - Power Apps" for detailed instructions. 2. Enable Change Tracking: Ensure that change tracking is enabled for the Finance and Operation tables you wish to export. 3. Disable Administration Mode: If the environment is in Administration mode, disable it by accessing the Power Platform Admin Center and toggling the Administration mode off. 4. Check Permissions: Verify that the user has the necessary permissions, including: - Dataverse System Administrator role. - Synapse Administrator role if linking with a Synapse Workspace. - Reader role access to the resource group containing the storage account and Synapse workspace. - Owner and Storage Blob Data Contributor role access for the Azure Data Storage. 5. Networking Configuration: Ensure that public network access is enabled for the linked storage account and that all IP addresses are allowed if linking to a Synapse Workspace. 6. Geography Check: Confirm that the Synapse workspace, storage account, and Power Apps environment are all created in the same geography.
If the issue persists after following these steps, further investigation may be required to identify additional underlying causes.