Wrong dataflow id in desktop - but working in service

[tdpwb]

Hi all,

We recently changed tenants and had to migrate all datasets and reports to the new ones. We replicated the dataflows we had in the new tenant and changed the ids in the datasets so they were pointing at the new ones. Everything is working fine online.

We are using source control with github to maintain the datasets and reports and keep track of the changes. I downloaded the most recent version of a dataset today and tried to refresh it on power bi desktop before making some changes and ¡surprise! Every dataflow connections is failing because the ids used are still from the old tenant. I have tried clearing the cache in settings but it still shows incorrect.

I am wondering what can I do? It seems like a local/profile/cache issue but not sure where to look.

Thanks in advance!

[v-kathullac]

Hi @tdpwb ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,

Chaithanya

[tdpwb · Accepted solution]

Hi, many thanks for your reply.

We tried the provided solution and didn't work. However we found a file named 'unappliedchanges.json' inside the pbi folder of the .semanticmodel folder that we deleted - that caused the dataflows to point to the correct tenant and id's again.

Not sure why this file existed since the model folders were downloaded directly from github and every dataset works correctly on the service.

Thanks a lot!

[v-kathullac]

Hi @tdpwb,

Thank you for reaching out to Microsoft Fabric Community Forum.

The issue might be cache issue can you please follow the below steps to overcone your issue.

• Clear permissions: Go to File > Options > Data Source Settings → Clear all permissions for the dataflow sources.

• Clear global cache: Go to %LOCALAPPDATA%\Microsoft\Power BI Desktop\AnalysisServicesWorkspaces and delete all folders there (Power BI must be closed).

• Ensure you’re logged into the correct tenant in Power BI Desktop

Regards

Chaithanya.