Some of the tables are not created with azure synapse link

Kvaratshelya, Vladimir 25 Reputation points
2024-08-13T19:05:25.55+00:00

I created an Azure Synapse Link for Dataverse in Azure Synapse Workspace.

The folders with Snapshot and csv files for each dataverse entity are created in Azure Data Lake Storage Gen2.

However, not all the tables are showing in workspace Lake database.

Example: Table X is not in lake database even if folder X (with files) exists in storage account.

There is no option to map these tables manually.

Any suggestions?

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,930 questions
Microsoft Dataverse Training
Microsoft Dataverse Training
Microsoft Dataverse: A Microsoft service that enables secure storage and management of data used by business apps. Previously known as Common Data Service.Training: Instruction to develop new skills.
34 questions
{count} votes

Accepted answer
  1. Smaran Thoomu 16,155 Reputation points Microsoft Vendor
    2024-08-26T14:08:39.6+00:00

    Hi @Kvaratshelya, Vladimir

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer .

    Issue: I created an Azure Synapse Link for Dataverse in Azure Synapse Workspace.

    The folders with Snapshot and csv files for each dataverse entity are created in Azure Data Lake Storage Gen2.

    However, not all the tables are showing in workspace Lake database.

    Example: Table X is not in lake database even if folder X (with files) exists in storage account.

    There is no option to map these tables manually.

    Any suggestions?

    Solution: I unlinked the Azure Synapse Link in Power Apps and then recreated it, choosing to import fewer tables than before. This resolved the issue we were experiencing. I believe the success was due to my decision to import fewer tables.

    If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

    I hope this helps!

    If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.


    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.