Forum Discussion
Dataverse table schema changed, Power BI remains on old schema, nothing helps
Hi Anonymous thanks for your advice. After a delay of about 12 hours the plattform propagated the schema changes. I mentioned this because my "fix" from above (removing columns by hand) suddenly threw errors (trying to remove columns that actually do not exist any longer). I guess I just saw some unusual platform behaviour. I am now able to work with the latest schema.
Hi ChrisBgt ,
Based on your description, you want to quickly get the latest updated table schema in dataverse in teams.
I checked the documentation and the easiest way is to use a solution, especially if you are not familiar with Dataverse. Solutions are used to move changes/configurations/customizations/architectures between environments and/or save/backup them. You can save the solution to a repository, or even unzip (more advanced) the solution to break it down into xml files for each component type. These files can then be committed to source code management (e.g. Azure DevOps) to get all the benefits of version control and conflict resolution.
Solved: Managing Dataverse Schema Changes - Power Platform Community (microsoft.com)
More on solutions: https://docs.microsoft.com/powerapps/developer/data-platform/introduction-solutions
More on unpacking solutions: https://docs.microsoft.com/power-platform/alm/use-source-control-solution-files
Or you can refer to the steps in this document to reconnect
View Dataverse for Teams table data in Power BI Desktop (preview) - Power Apps | Microsoft Learn
Create a Power BI report using the Dataverse connector - Power Apps | Microsoft Learn
Best regards,
Albert He
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi Anonymous thanks for your advice. After a delay of about 12 hours the plattform propagated the schema changes. I mentioned this because my "fix" from above (removing columns by hand) suddenly threw errors (trying to remove columns that actually do not exist any longer). I guess I just saw some unusual platform behaviour. I am now able to work with the latest schema.