Forum Discussion

EaglesTony's avatar
EaglesTony
Post Prodigy
1 year ago
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...
Need Help
  • EaglesTony's avatar
    EaglesTony
    1 year ago

    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"

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Thanks for the reply from pborah and saud968 , please allow me to provide another insight:

Hi, EaglesTony 

Could you please let me know if the responses from pborah and saud968 have resolved your issue? If it did, kindly accept them as the solution.
 

You might also consider leaving the step of creating a new column in Power Query. This way, you won't encounter circular dependency errors when referencing this column.
 Below is a screenshot of the relevant documentation for custom columns in Power Query:

For more details, please refer to the following link:

Add a custom column in Power BI Desktop - Power BI | Microsoft Learn

 

Best Regards,

Leroy Lu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.