Lakehouse tables (all) showing as unindentified

[dennisau]

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

[v-pbandela-msft]

Hi @dennisau,

I wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.
If the community member's answer your query, please mark it as "Accept as Solution" and select "Yes" if it was helpful.
If you need any further assistance, feel free to reach out.

Thank you,
Pavan.

[dennisau]

Hi Pavan,

Please see my response dated ‎01-20-2025 09:30 AM.  Thanks.

[v-pbandela-msft]

Hi @dennisau,

Thank you for reaching out in Microsoft Community Forum.

Please follow the below steps To acheive the error:

1.verify that the necessary read/write permissions are granted for the tables.

2.Confirm that the tables are in a supported format (e.g., Delta, Parquet) and the schema is correctly aligned with Power BI’s requirements.

3.Refresh the data source to re-establish the connection, or if issues persist, clear and recreate the data source.

If you found this post helpful, please consider marking it as "Accept as Solution" and select "Yes" if it was helpful. help other members find it more easily.

Thank you,
Pavan.

[v-pbandela-msft]

Hi @dennisau,

I wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.
If the community member's answer your query, please mark it as "Accept as Solution" and select "Yes" if it was helpful.
If you need any further assistance, feel free to reach out.

Thank you,
Pavan.

[v-pbandela-msft]

Hi @dennisau,

Thank for reaching out in Microsoft Community Forum.

I trust @jennratten  response is accurate and will address your issue.

If you have any further questions or updates regarding your issue, feel free to ask, and we will look into that.

If the Super User's answer meets your requirements, please consider marking it as the "Accepted as  Solution"

Regards,
Pavan.

[jennratten]

Hi @dennisau - thanks for posting.

New lakehouse tables can sometimes temporarily appear in a folder named Unidentified, while they are still being finalized - and then and they are finalized they move out of the folder and the folder goes away.  Do your tables still appear like this after refreshing the screen?

If you are still seeing the tables in the Unidentified folder then it could mean that the tables are not properly registered or there is some kind of issue with the metadata.  Here are some things to check:

• Confirm the schemas are set up properly Dataverse.
• Confirm that in the Synapse Link settings all required fields are selected for sync and entity relationships are present.

For the one table that is showing the Error Code 403 Forbidden - this typically indicates a permission issue.  Here are some things you can check:

• Verify that the Synapse Link service, managed identity/service principal have the necessary permission to access the storage account and the Dataverse environment. 
• The link service will need owner access to the storage account.
• Verify that the Power Platform environment is not in administration mode.

I hope this info helps.  Please let me know if you need further assistance.

[dennisau]

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

[v-pbandela-msft]

Hi @dennisau,

Thank you for reaching out in Microsoft Community Forum.

Sorry to know it didn’t help. Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious.

Below is the link to create Microsoft Support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

Please continue using Microsoft community forum.

Regards,
Pavan.