Forum Discussion
Solved
How to fix Circular reference in Data Relationship
Hi, I have a slicer that uses a column(Sprint) in a table(SprintDates). I have table1 that I calculated a column(Sprint) that works. I then(via a lookupValue) created a new column(S...
All I figured this out, it had to do with setting up the relationships as Single instead of Both, which caused the amiguous error.
Basically, I have a top table called Team, I connected this as a single connection to the "child tables" based off a key (some of the fields in the child tables were also used in slicers) and this fixed the issue, so have to be careful with "both"
A way to get around this is to create these tables in the transform data stage and then load everything and create relationships.
Additionally, do break the indirect relationships that Power BI automatically creates as mentioned by another user.