We are using Synapse Link for Dataverse feature to bring dynamics 365 data to ADLS and Synapse Analytics. We have below open issues due to which we are unable to finalize the solution: In F&O linked dataverse environment, we have created a synapse link where in managed tables, all the F&O tables are not showing up (we have followed all the pre-requisites as per the MS documents and using [?athena.enableFnOTables=true] once the synapse link is created to view F&O tables). As we have more than 1000 tables as per MS documents to activate more than 1000 tables we need to create new synapse link, so we tried creating new synapse link in same dataverse environment and getting the error - “Folder’s container endpoint and path or security group match with an existing folder.” 3. We are getting error while activating the available tables in synapse link “ An internal error occured, the profile is in Error state”. These are the major 3 open issues for which we are unable to get the solution and right direction, which is stopping us to take the decision of using azure synapse link for dataverse as an final solution for bringing data from the dynamics platform. Also need help for dynamics CRM synapse link configuration ad we are not able to see the CRM tables in crm dataverse synapse link environment. Please suggest clear steps to make available all the tables of dynamics 365 f&o and CRM in synapse link, as we are not able to get the exact tables and lots of them are missing from the list.

Azure Synapse Link for dataverse to bring Dynamics 365 data to ADLS and Synapse for analytical purpose - Facing Issues and inconsistencies in the feature

Sriram M 0

We are using Synapse Link for Dataverse feature to bring dynamics 365 data to ADLS and Synapse Analytics. We have below open issues due to which we are unable to finalize the solution:

In F&O linked dataverse environment, we have created a synapse link where in managed tables, all the F&O tables are not showing up (we have followed all the pre-requisites as per the MS documents and using [?athena.enableFnOTables=true] once the synapse link is created to view F&O tables).
As we have more than 1000 tables as per MS documents to activate more than 1000 tables we need to create new synapse link, so we tried creating new synapse link in same dataverse environment and getting the error - “Folder’s container endpoint and path or security group match with an existing folder.” 3. We are getting error while activating the available tables in synapse link “ An internal error occured, the profile is in Error state”. These are the major 3 open issues for which we are unable to get the solution and right direction, which is stopping us to take the decision of using azure synapse link for dataverse as an final solution for bringing data from the dynamics platform. Also need help for dynamics CRM synapse link configuration ad we are not able to see the CRM tables in crm dataverse synapse link environment.

Please suggest clear steps to make available all the tables of dynamics 365 f&o and CRM in synapse link, as we are not able to get the exact tables and lots of them are missing from the list.

Harishga 4,875 Reputation points Microsoft Vendor

2024-05-21T17:32:59.6+00:00
Hi @Sriram M

Welcome to Microsoft Q&A platform and thanks for posting your question here.

I understand that you are facing issues with Azure Synapse Link for Dataverse. Going through each problem step by step can lead us to a solution.

F&O Tables Not Showing in Managed Tables:

Double-check that the feature flag ?athena.enableFnOTables=true is correctly appended to the URL when accessing the Synapse Link.

Verify that the F&O environment is updated to a version that supports Synapse Link integration.

Error Creating New Synapse Link:

The error message indicates a conflict with an existing folder’s path or security settings. Make sure that the new Synapse Link has a unique container endpoint, folder path, and security group.

If the issue persists, consider deleting the existing Synapse Link and recreating it with distinct settings.

Error Activating Tables in Synapse Link:

This error can occur due to various reasons, including service outages or misconfigurations. Check the Azure Service Health for any ongoing issues.

Try deactivating and reactivating the tables. If the error continues, you may need to delete and recreate the Synapse Link profile.

For Dynamics CRM Synapse Link Configuration:

Confirm that change tracking is enabled for the CRM tables you wish to sync.

Check if there are any filters applied that might be excluding the CRM tables from being listed.

Ensure that the CRM environment meets all the prerequisites for Synapse Link integration.

Here are the steps to make all the Dynamics 365 F&O and CRM tables available in Synapse Link, based on the documentation:

Prerequisites:

Ensure that you have the required application versions for Dynamics 365 F&O. The feature is generally available with finance and operations application versions 10.0.36 (PU60) cumulative update 7.0.7036.133 or later.

Confirm that change tracking is enabled for the Dynamics 365 CRM tables you want to export.

Add Finance and Operations Tables:

In the Power Apps maker portal, navigate to the Azure Synapse Link area and select ‘Manage tables’ to add or remove linked tables.

Use the feature flag ?athena.enableFnOTables=true to view and manage F&O tables in Azure Synapse Link.

Access Incremental Data Changes:

Set up continuous replication of entity and table data to capture create, update, and delete transactions.

Working with Data and Metadata:

Ensure that data is stored in the Common Data Model format for semantic consistency across apps and deployments.

Save data in Parquet Delta Lake format for faster query response times.

Enable Finance and Operations Data Entities:

Choose both standard and custom finance and operations entities and tables for replication.

Link or unlink the environment to Azure Synapse Analytics and/or Data Lake Storage Gen2 in your Azure subscription without going to the Azure portal or Microsoft Dynamics Lifecycle Services.

Reference:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-select-fno-data
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-synapse

Hope this helps. Do let us know if you any further queries.
Harishga 4,875 Reputation points Microsoft Vendor

2024-05-22T09:57:15.17+00:00

Hi @Sriram M
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sriram M 0 Reputation points

2024-05-25T04:11:10.6966667+00:00
Hi @Harishga ,

Thank you for your guidance. We have followed all the steps you outlined, but we are still experiencing the same issues. Here is a detailed explanation of what we have done and the problems we are facing:

Issue 1: F&O Tables Not Showing in Managed Tables

Action Taken:

• I appended the feature flag ?athena.enableFnOTables=true to the URL when accessing the Synapse Link.

• Verified that my F&O environment is updated to a version that supports Synapse Link integration.

Current Status:

• Despite these steps, the F&O tables are still not visible in the managed tables section.

Issue 2: Error Creating New Synapse Link

Action Taken:

• Ensured that the new Synapse Link has a unique container endpoint, folder path, and security group.

• Tried deleting the existing Synapse Link and recreated it with distinct settings.

Current Status:

• The error persists, indicating a conflict with an existing folder’s path or security settings.

Issue 3: Error Activating Tables in Synapse Link

Action Taken:

• Deactivated and reactivated the tables.

• Deleted and recreated the Synapse Link profile.

Current Status:

• The error continues to occur, preventing table activation.

• Need to check Azure Service Health for ongoing issues.

Issue 4: Dynamics CRM Synapse Link Configuration

Action Taken:

• Confirmed that change tracking is enabled for the CRM tables.

• Checked for any filters that might be excluding the CRM tables.

• Verified that the CRM environment meets all prerequisites for Synapse Link integration.

Current Status:

• The CRM tables are still not syncing as expected.

Additional Information

• Environment Details:

-Already shared with MS support team

• Azure Synapse Link version: don't have version for azure synapse link

• F&O environment version: 10.0.39

• CRM environment version: 9.2

• Error Messages:

Error1- "Folder's container endpoint and path or security groups match with an existing folder.",

Error 2- "An internal error occurred, the profile is in error state"

• Steps to Reproduce:

Trying to create a new synapse link by selecting enterprise policy and synapse connection with selecting our azure subscription and adls container we are getting error 1.

Selecting 1000 tables and below tables in existing azure synapse link to activate we are getting error 2

Request for Further Assistance

Given the detailed steps and issues above, could you provide more specific troubleshooting steps or insights? Any additional documentation or support resources would also be appreciated.

Thank you for your assistance.

Best regards,

Sriram M

Share via

Azure Synapse Link for dataverse to bring Dynamics 365 data to ADLS and Synapse for analytical purpose - Facing Issues and inconsistencies in the feature