Forum Discussion
Hidden relationship?
the message actually says it quite clearly. Currently there is a following setup:
- 'queues' => 'systemusers'
- 'queues' => 'trs_tasktypes'=>'tasks'
so if you add 'systemusers'=>'tasks' then filter on 'queues' could follow 2 paths to filter 'tasks': either the path 2. or this one:
- 'queues' => 'systemusers'=>'tasks'
which causes the ambiguity. The question is which logic you want to implement. If it difers per case then you can activate the inactive relationship by using USERRLATIONSHIP, e.g. in CALCULATE https://dax.guide/userelationship/
more general info on relationships (around 14:30 Alberto starts talking about ambiguity):
https://www.sqlbi.com/tv/understanding-relationships-in-power-bi/
most likely you have bidirectional relationships involving other tables, that are indirectly creating a relationship between the 2.
I would suggest changing the bidirectional relationships to single direction (bidirectional relationships are generally a bad idea in DAX, see more here https://www.sqlbi.com/tv/understanding-relationships-in-power-bi/)
if you post the screen of all your relationships I could then specify which path is causing the issue exactly
the message actually says it quite clearly. Currently there is a following setup:
- 'queues' => 'systemusers'
- 'queues' => 'trs_tasktypes'=>'tasks'
so if you add 'systemusers'=>'tasks' then filter on 'queues' could follow 2 paths to filter 'tasks': either the path 2. or this one:
- 'queues' => 'systemusers'=>'tasks'
which causes the ambiguity. The question is which logic you want to implement. If it difers per case then you can activate the inactive relationship by using USERRLATIONSHIP, e.g. in CALCULATE https://dax.guide/userelationship/
more general info on relationships (around 14:30 Alberto starts talking about ambiguity):
https://www.sqlbi.com/tv/understanding-relationships-in-power-bi/
Such a shame that Power BI does not always list which tables are causing the problem. In this case it listed queues and tasks, but as I write this in 2023, when I see such a message there, is no indication as to which of the dozens of tables are causing the problem. But thank you for describing the issue in terms I can understand. I will, at least, know where to look from not on!
