Dataverse table schema changed, Power BI remains on old schema, nothing helps

[ChrisBgt]

I started using a Dataverse-in-Teams-Table some time ago for a Power BI report. Recently, I changed the table schema: I added new columns, and removed some columns. Now I am trying to build a new report using the schema. For the columns removed, I get this error message:

I could "fix" this problem by extending the query and manually remove columns that do not exist anymore, but this approach leads to problems after restarting Power BI:

let
Source = CommonDataService.Database("orga5348445.crm17.dynamics.com"),
dbo_crac4_bedanalyse = Source{[Schema="dbo",Item="crac4_bedanalyse"]}[Data],
#"remove" = Table.RemoveColumns(dbo_crac4_bedanalyse, {"crac4_bedurfnisbeschreibung","crac4_checkcoach","crac4_checkcoachname","crac4_checkgs","crac4_checkgsname"})
in
remove

Now two questions:

• How to properly adapt to the new schema (than removing columns manually one by one)?
• How to bring in the columns newly added to Dataverse?

What I tried, without success:

• publish Dataverse table (using the PowerApps frontend that I called from PowerApps in Teams)
• In Power BI: close and reopen connection
• In Power BI: empty data cache
• restart Power BI, PC
• Using transform data instead of get data
• Using direct query

Many thanks for your help! I was searching for possible solutions for hours, but nothing really helped. It seems really weird to me that Power BI comes up with an old schema that has been changed long ago, and that just doesn't want to vanish. 
Chris

[Anonymous]

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

[ChrisBgt · Accepted solution]

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.