Power BI Dataverse Connection Not Reflecting Schema Changes

Question

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.&nbsp;Steps I've already tried:1/Deleting credentials and logging in again&nbsp;2/Re-published tables in Dataverse3/Creating a new connection.4/Clearing cache5/Testing on a new computer to rule out cache issues.6/ Waited for over 24 hours just in case there is a delay&nbsp;&nbsp;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?&nbsp;&nbsp;Any help or suggestions would be greatly appreciated. Thank you!

pbi_2004 · Accepted Answer

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

Forum Discussion

Related content

Missing Connection Details - Dataverse

Connectivity Issue : Power BI to dynamics 365 (Dataverse)

Updates not reflected

Issue connecting Azure synapse link for Dataverse

Mirrored Dataverse in Fabric