Changes to Dataverse table structure not coming through to Power BI

[Keira_B]

We removed a column from a table in dataverse, added a couple of new columns, and added a new table. Prior to doing this my colleague had connected to the original table without any issues. After removing the column he started getting an "invalid column name" error. The error comes up as soon as the table is selected, so it's not a Power Query error. If I add a line to power Query to remove the column that was deleted then it loads the table, but without the 2 new columns (which we need).  

Deleting the data source and clearing the data cache didn't resolve the issue. 

I connected to the dataverse for the first time and I'm also getting the invalid column name error, and the new table we added also doesn't show up in the list of tables. It's been a week since these changes were made.

Can anyone shed some light on how we can get our dataverse updates to appear in Power BI? (The changes in Dataverse have been published)

[pbi_2004]

If none of the above solutions work for you, it might be an issue with your environment settings.
If the environment is in administration mode, it could restrict your access to make changes to the data schema.
In this case, you should contact your IT team to disable administration mode.
This solution worked for me.

[Roberta_T]

Microsoft Help Desk solved this issue for us by advising us to do the following:

"If the customer is using a TDS connection to pull the data. If they are, this could be a problem with the TDS 
endpoint metadata not getting refreshed (If these are new or modified fields for example).

To refresh this, please turn off the TDS endpoint in PPAC and then toggle it back on again. This will refresh the metadata. "

[pbi_2004]

im facing the same issues and tried all of the above and none of them works.

Any other solution?

Odata feed works but I need direct query mode....

Any help is very appreactiated 

[ChrisBgt]

I am running into the same issue ... no way out 😐

[mavii1981]

Hey Chris. I found the solution was to go in to power query. On that data table hide a column. Then once hidden go back in and unhide it and the new columns will appear. Apparently sorting the columns works too.

[ChrisBgt]

doesn't do the trick on my site, unfortunately. But thx anyways ...

[mavii1981]

Hey! Did you get a solution for this as i had the exact same thing happen to me. Cleared and reconnectef to dataverse multiple times without success. Any updates would be very helpful. 

[Keira_B]

I was never able to resolve this using the Dataverse connector. Ended up connecting using the OData feed option instead, and that's been working fine.

[Anonymous]

Hi @Keira_B 

I understand your issue, after modifying the Dataverse table structure, Power BI displays an "invalid column name" error and does not reflect the new changes.

Ensure that all changes made to the Dataverse table structure have been published. This step is crucial for making sure that the latest metadata, including the schema changes, is available to Power BI.

After confirming that all changes in Dataverse have been published, go to Power BI, remove the existing Dataverse data source, and then reconnect to ensure that Power BI fetches the latest schema. 

• In Power BI Desktop, go to Home Tab -> Transform Data -> Data Source Settings
• Select the dataverse data source and click Clear Permissions
• Click Delete and confirm
• Close the Data Source Settings window and click Get Data -> Dataverse
• Enter the correct instance URL
• Select the tables you want to import or use DirectQuery
• Click Load

Regards,

Nono Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Keira_B]

Thanks Nono, but unfortunately we've been through that process a few times and it hasn't worked.

Because I had the same issue as my colleague when I hadn't previously connected to Dataverse (so not a cache issue), it does seem like a publishing issue at the Dataverse end, but each time we try it confirms it has published successfully.

[pbi_2004]

If none of the above solutions work for you, it might be an issue with your environment settings.
If the environment is in administration mode, it could restrict your access to make changes to the data schema.
In this case, you should contact your IT team to disable administration mode.
This solution worked for me.