ContributionsMost RecentMost VotedSolutionsRe: Lakehouse tables (all) showing as unindentified Hi Pavan, Please see my response dated 01-20-2025 09:30 AM. Thanks. Re: Lakehouse tables (all) showing as unindentified Hi, This is still an isuse and persisting. I abandoned Microsoft Fabric and just stick with Azure Synapse Analytics workspace to implement reporting requirements via Power BI and Power BI bulder for paginated reports. Please find my reponse below: Confirm the schemas are set up properly Dataverse. - This was setup properly and working Confirm that in the Synapse Link settings all required fields are selected for sync and entity relationships are present. - Azure Synapse Link for Dataverse all required fields are selected and tables selected both for D365 CE and F&O. Verify that the Synapse Link service, managed identity/service principal have the necessary permission to access the storage account and the Dataverse environment. - Permission is properly set since default Microsoft One Lake can write/update to the resource group in the storage account. The link service will need owner access to the storage account. - Permission is properly set since default Microsoft One Lake can write/update to the resource group in the storage account. Verify that the Power Platform environment is not in administration mode. - Dataverse environment (instance) is not in admin mode Lakehouse tables (all) showing as unindentified Lakehouse tables (all) showing as unindentified Lakehouse was created via link from Azure Synapse Link for Dataverse. Workspace Azure connections: Tenant Level Storage: Azure Data Lake Gen2 storage account Fabric capacity : F4 Solved
Data PrivacyMicrosoft Fabric Community and Privacy To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide. Read the guide
