Forum Discussion
Model relationships breaking unexpectedly when visualizing Planning table columns in Power BI
Hi Databasic - Only keep Name → Planning and Name → RM_Film relationships as single-directional (one-to-many, from Name to Planning/RM_Film). That’s usually safest.
When both are set to bidirectional, Power BI may struggle to resolve filter propagation, especially when you try to pull data into a single visual that includes columns from all three tables errors like , ambiguous filter paths. Avoid bidirectional joins unless truly needed.
suggest you, make them single-direction from Name → Planning and Name → RM_Film.Use that table for your ERP export visuals/reports — reliable and isolated from model quirks.If needed, use slicers from Name or Fixed tables to make dynamic test versions.
Bidirectional relationships and ambiguity in DAX - SQLBI
Hope this helps.
Hi Databasic - Only keep Name → Planning and Name → RM_Film relationships as single-directional (one-to-many, from Name to Planning/RM_Film). That’s usually safest.
When both are set to bidirectional, Power BI may struggle to resolve filter propagation, especially when you try to pull data into a single visual that includes columns from all three tables errors like , ambiguous filter paths. Avoid bidirectional joins unless truly needed.
suggest you, make them single-direction from Name → Planning and Name → RM_Film.Use that table for your ERP export visuals/reports — reliable and isolated from model quirks.If needed, use slicers from Name or Fixed tables to make dynamic test versions.
Bidirectional relationships and ambiguity in DAX - SQLBI
Hope this helps.
This web page gave me the right understanding of relations to troubleshoot. I had to dive into the data and was able to pull out some duplicates to remove the indirect many to many relation. Resolved, thanks a lot 💪
