Forum Discussion
Fabric Dataverse/CRM Virtual Table Metadata Refresh
Hello,
I am working in my Fabric Lakehouse and Dataverse. I have tables in my lakehouse that serve as a source for virtual tables in Dataverse. I have already created the virtual tables, relationships, forms, and views, etc. Now, I need to add more columns to these tables, but there doesn't appear to be a way to refresh the metadata for the new columns that I just added in the lakehouse tables to show in the virtual tables. The only way I know to do this is to delete the virtual table and recreate them, but that means that I have to delete everything else, as well, including relationship, form, and views.
I have researched it and it seems to be a limitation at this time. Does anyone have any ideas on how to accomplish this? Is this something that I need to bring up as a new idea? Surely, someone else has stumbled upon this.
I would greatly appreciate any tips!
Thanks! Mark 🙂
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.
-
2 Replies
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.
-
