Dataverse to Microsoft Fabric Link should gracefully handle unsupported tables instead of blocking metadata generation
When using Dataverse → Microsoft Fabric Link, a single Dataverse table with an unsupported configuration (for example, a logical name exceeding Fabric shortcut limits) can cause shortcut creation to fail. This prevents Fabric from generating critical metadata tables (OptionsetMetadata, StateMe...
When using Dataverse → Microsoft Fabric Link, a single Dataverse table with an unsupported configuration (for example, a logical name exceeding Fabric shortcut limits) can cause shortcut creation to fail. This prevents Fabric from generating critical metadata tables (OptionsetMetadata, StateMetadata, StatusMetadata, TargetMetadata), even when all other tables are valid. This commonly occurs with Microsoft‑generated system tables (for example, Event Management / Marketing tables) and is not caused by customer misconfiguration. Suggested improvement: Skip or isolate unsupported tables instead of failing the entire link. Continue generating metadata tables for supported entities. Surface clear, actionable diagnostics identifying the specific table causing the failure. This would improve reliability, reduce analytics outages, and significantly lower escalation volume for enterprise customers.
Problem:
When using Dataverse → Microsoft Fabric Link, there is currently no native monitoring, logging, or alerting capability in Dataverse to detect link failures or synchronization issues. Failures (such as shortcut creation errors, missing metadata tables, or incompl...
Lack of Native Monitoring and Failure Diagnostics for Dataverse → Microsoft Fabric Link
Problem:
When using Dataverse → Microsoft Fabric Link, there is currently no native monitoring, logging, or alerting capability in Dataverse to detect link failures or synchronization issues. Failures (such as shortcut creation errors, missing metadata tables, or incompl...