Connection to Semantic model refuses to update model & finds ambiguous paths that don't exist

[SevsBo]

We have Report 2 connected via Direct Query to a semantic model from Report 1, where we have recently changed part of the model.

 

Report 1 was successfully republished and, even if we download it again, we can clearly see the changed we made.

Report 2, however, refuses to update to the latest model and instead throws an interesting error:

 

This seems like a modelling issue until we look at the model that now exists in Report 1:

There used to be a relationship between Table 2 and Table 3 in the old model, but at the same time there was no relationship between Table 1 and the blank table prior to Table 3. This entire path was reworked in the new model, and Report 1 never had any errors with either configuration as there were no ambigious paths.

Report 2, however, seem to think that the old connection still exists, but at the same time tries to add the new connection between Table 1 and the blank table to connect to Table 3.

I cannot manually update the report due to this error, and nothing changes if I try to update the report on PBI Service. How can I clear this legacy data from Report 2 without having to completely redo the entire report?

Update: I have tried changing source to re-connect to the Semantic model. Same issue appears. But if I create a blank report and connect to the same semantic model, everything is OK.

 

[v-tejrama]

Hi @SevsBo ,

Has your issue been resolved?If the response provided by @mh2587  addressed your query, could you please confirm?

It helps us ensure that the solutions provided are effective and beneficial for everyone.
If yes, kindly accept the useful reply as a solution and give us Kudos. It would be appreciated.
Thank you for your understanding!

[v-tejrama]

Hi @SevsBo ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[mh2587]

Delete Metadata ( Try this Work around to clear and delete metadata might resolve your issue)
Note. Be sure to duplicate this file avoid changing in original one

If you're using a PBIP or source-controlled .pbit or .pbip format:

1. Open the folder structure.

2. Look for the Model.bim or DataModelSchema files.

3. Manually inspect and remove any stale relationship definitions.

4. Reopen the model in Power BI Desktop.

[SevsBo]

I am not using PBIP. How can I delete metadata, please?

[v-tejrama · Accepted solution]

Hi @SevsBo ,

Thank you for following up.

Since you're using PBIX instead of PBIP format, you can't directly delete metadata files like Model.bim. However, the “ambiguous path” error usually occurs because Power BI retains cached schema or relationship information from the semantic model. Even after updating and publishing Report 1, Report 2 may still reference outdated metadata, which leads to this issue.

Here's how you can resolve it: Open Report 2, switch to Model view, and try removing the existing semantic model connection. If that’s not an option, delete all visuals and tables using the model, then reconnect via Get Data > Power BI Datasets and choose the updated Report 1. This will ensure Power BI loads the latest schema and discards any cached data.

If the problem persists, creating a new blank PBIX file and reconnecting to the updated semantic model is the most effective solution. Rebuilding the visuals from scratch guarantees a clean setup with no legacy conflicts.

The original advice for PBIP users remains accurate, and for PBIX users, this method delivers the same results through the UI. You’ll be able to resolve the issue efficiently with these steps

Thank you,

Tejaswi.

[SevsBo]

Thank you, @v-tejrama,
I was afraid that was the only option, so we have simply rebuilt the report. It's annoying that PBI does this and the only solution is to rebuild, but here we are.