Forum Discussion
Maintenance on Lakehouse Tables
Hi rtolsma ,
I believe the issue is that the Dataverse data is not actually managed by Fabric, tables are pointers to your dataverse environment, the error while annoying is correct.
Yup makes sense that this is a short cut into an ADLS Gen 2 storage facility that the Fabric instance doesn't have access to. So impossible to maintain, but I didn't realize that shortcuts would cause you to also increase your OneLake storage...seems like I'm doing exactly what was told us was the benefit, no data duplication but it appears that I'm consuming Dataverse storage and OneLake storage as well.
The Docs here, https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-view-in-fabric#direct-access-to-your-data-in-microsoft-onelake, say
When you link to Fabric from Power Apps, the system creates an optimized replica of your data in delta parquet format, the native format of Fabric and OneLake, using Dataverse storage such that your operational workloads aren't impacted. Is it possible that onelake was chosen as the destination?
With Fabric Link (a.k.a. "Link to Fabric") the OneLake is the only option available which is always created when tables are exported from D365 Sales or from D365 Finance and Operations.
Really appreciate all the suggestions! I think I have a pretty good idea how to move forward.