Forum Discussion
Odd Ambiguous Paths error on data load
We're using a live connection to other semantic models and while updating the data, the following error was returned.
Direct Query to ABC
Failed to save modifications to the server. Error returned:
'There are ambiguous paths between 'Table1' and 'Table2':
'Table1'->'Table2' and 'Table1'->'Table2' '.
This basically tells me there's no problem but somehow it's a problem?
Hi SevsBo ,
Yeah, that error message is definitely one of the more confusing ones — but it usually points to a modeling issue with relationships when using DirectQuery to other semantic models.
Here’s what’s likely happening:
Power BI is detecting multiple relationship paths between Table1 and Table2, even if they look identical. This can happen when:
- You have two or more semantic models connected via DirectQuery, and both contain similar or overlapping tables.
- There are inactive relationships or auto-created relationships that Power BI is trying to resolve during query execution.
- The model includes composite models where ambiguity isn't always obvious in the diagram.
What you can try:
- Open the model view and check all relationships between Table1 and Table2. Even if they look the same, Power BI might be seeing them as separate paths.
- If you find multiple paths, try deleting or deactivating one of them — especially if one is not needed for your current logic.
- If you're using composite models, consider using TREATAS() or USERELATIONSHIP() in your DAX to control which path is used explicitly.
- Also, check if any auto-generated relationships were created when you connected to the semantic model — these can sometimes cause hidden ambiguity.
Let me know if you want to share a screenshot of your model diagram — happy to help pinpoint the exact cause.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was supported by AI for translation and text editing.
3 Replies
Hi SevsBo ,
This is related with the relationships you have on your model, meaning that you must have some tables that have relationships that are refering different paths between those two tables.
Check the relationships of table 1 and 2 and all the associeted ones to check if there is no path that can be doubling trough another table.
Hi SevsBo ,
Yeah, that error message is definitely one of the more confusing ones — but it usually points to a modeling issue with relationships when using DirectQuery to other semantic models.
Here’s what’s likely happening:
Power BI is detecting multiple relationship paths between Table1 and Table2, even if they look identical. This can happen when:
- You have two or more semantic models connected via DirectQuery, and both contain similar or overlapping tables.
- There are inactive relationships or auto-created relationships that Power BI is trying to resolve during query execution.
- The model includes composite models where ambiguity isn't always obvious in the diagram.
What you can try:
- Open the model view and check all relationships between Table1 and Table2. Even if they look the same, Power BI might be seeing them as separate paths.
- If you find multiple paths, try deleting or deactivating one of them — especially if one is not needed for your current logic.
- If you're using composite models, consider using TREATAS() or USERELATIONSHIP() in your DAX to control which path is used explicitly.
- Also, check if any auto-generated relationships were created when you connected to the semantic model — these can sometimes cause hidden ambiguity.
Let me know if you want to share a screenshot of your model diagram — happy to help pinpoint the exact cause.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was supported by AI for translation and text editing.
It's a strange one as I can only see one instance of each table in the model we have brought over, and they're connected via a one-way relationship. But I think you're right, there might be an error somewhere else in the model it's drawing from, as we're not bringing across all tables.
