Forum Discussion

pbi_2004's avatar
pbi_2004
Frequent Visitor
1 year ago
Solved

Power BI Dataverse Connection Not Reflecting Schema Changes

I recently made changes to my Dataverse schema by adding new columns and a new table. However, when I try to edit my Power BI report, it still shows the old structure. Here's what I've observed:

1. The OData connection shows the new columns and table correctly. but I need to use DirectQuery, so switching to OData is not an option.
2/ Power Apps displays the new columns correctly.
3/This issue only occurs in Power BI.

 

Steps I've already tried:

1/Deleting credentials and logging in again 
2/Re-published tables in Dataverse
3/Creating a new connection.
4/Clearing cache
5/Testing on a new computer to rule out cache issues.

6/ Waited for over 24 hours just in case there is a delay 

 

None of these solutions have resolved the problem. The Power BI report continues to show the old schema despite the changes made in Dataverse.

Questions:

1/Are there any known issues with Power BI not refreshing Dataverse schema changes?
2/Are there any specific steps to force Power BI to recognize schema updates in Dataverse?
3/Could there be any settings in Dataverse or Power BI that might be preventing the schema update from being recognized?

 

 

Any help or suggestions would be greatly appreciated. Thank you!

  • After about 2-3 days of delay the plattform propagated the schema changes. So problem solved

2 Replies

  • pbi_2004's avatar
    pbi_2004
    Frequent Visitor

    one more clue : this table has been restored from a backup

    I tested with normal table and new colunn is showing fine

  • pbi_2004's avatar
    pbi_2004
    Frequent Visitor

    After about 2-3 days of delay the plattform propagated the schema changes. So problem solved