Odd Ambiguous Paths error on data load

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:

1. 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.
2. If you find multiple paths, try deleting or deactivating one of them — especially if one is not needed for your current logic.
3. If you're using composite models, consider using TREATAS() or USERELATIONSHIP() in your DAX to control which path is used explicitly.
4. 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.