Forum Discussion
Unable to make relationship active
I know there's some ambiguity issue since I have multiple relationships happening, but i'm not sure as to what the solution should be. I basically want to have the bottom timeline be filtered on whatever I have selected. The three top charts are all separate tables, and this only works on whatever relationship I have active at the time (can only activate one). I also tried using a Measure which was = to whatever was selected and tried filtering on that, but I'm not sure if that's how that's supposed to work or I just messed up the syntax.
I ended up resolving this very simply by continuing the one to many relationship from Subsites22 to the AllDataTable, and removing the other links to the AllDataTable.
13 Replies
This is becuse if you active this relationship if you filter on Top Level for example, there would be multiple paths to AllDateTable.
Please go to the Circular dependencies in relationships section in this SQLBI article to learn more
Those 3 table look almost the same, could they be combined?
Thanks for the response. I have to break them up into separate tables to get the relationships working the way I intended. When I click the leftmost table, the second table is filtered on the selection and so on and so forth. I've tried doing this with other methods such as drill down but to no avail.
Hi SeanDrayton
If activating an inactive relationship results in multiple connection paths between two tables, Power BI blocks it to prevent ambiguity in DAX calculations. For instance, if TopLevel already connects to AllDataTable through an active relationship, introducing another path via Subsites11 can cause conflicts.
Currently, TopLevel has an active relationship with Subsites11, and Subsites11 is linked to AllDataTable. If an additional active relationship is established directly between Subsites11 and AllDataTable, it would create two distinct paths between them, leading to ambiguity. To avoid this, Power BI restricts the activation of another relationship.
I understand why it's restricted due to ambiguity, but am unclear on how to acheive the desired result. Do you have a suggestion?
It is difficult to propose a solution without seeing the model itself. But you could use USERELATIONSHIP to invoke an inactive relationship.
Hi SeanDrayton
You could use USERELATIONSHIP function to make the relationship active. PFB syntax
USERELATIONSHIP (table1[column_name], table2[Column_name])
Thanks
Hi SeanDrayton
Thank you for reaching out microsoft fabric community forum.May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
I ended up resolving this very simply by continuing the one to many relationship from Subsites22 to the AllDataTable, and removing the other links to the AllDataTable.
