Forum Discussion
Fabric Dataverse/CRM Virtual Table Metadata Refresh
you are not missing anything, the refresh capability simply does not exist yet. This is currently a real limitation in how virtual tables work with lakehouse backed sources. When schema changes happen in the lakehouse, virtual tables in Dataverse do not automatically resync metadata, and there is no supported refresh action today. The platform treats the virtual table definition as fixed after creation.
Your options right now are limited to:
-
recreate the virtual table (clean but disruptive), or
-
create a new virtual table with the updated schema and migrate forms, views, and relationships manually via solution export/import to reduce rework.
-
you are not missing anything, the refresh capability simply does not exist yet. This is currently a real limitation in how virtual tables work with lakehouse backed sources. When schema changes happen in the lakehouse, virtual tables in Dataverse do not automatically resync metadata, and there is no supported refresh action today. The platform treats the virtual table definition as fixed after creation.
Your options right now are limited to:
-
recreate the virtual table (clean but disruptive), or
-
create a new virtual table with the updated schema and migrate forms, views, and relationships manually via solution export/import to reduce rework.
Thank you for the quick reply, Vinodh!
Do you know if an initiative is already listed in the roadmap? Should I bring up the idea? I want to make sure it gets some consideration.