How to fix Circular reference in Data Relationship

Understand the Circular Dependency:
A circular dependency occurs when two or more tables are interdependent, creating a loop that Power BI cannot resolve.

Review Your Relationships:
Check the relationships between SprintDates, table1, and table2. Ensure that there are no indirect relationships causing the circular dependency.

Break the Circular Dependency:
One way to break the circular dependency is to use a bridge table. This table will act as an intermediary to connect your tables without creating a loop.

Create a Bridge Table:
Create a new table (e.g., BridgeTable) that contains unique values of the Sprint column.
Establish relationships between BridgeTable and the other tables (SprintDates, table1, and table2).

Modify Relationships:
Set up the relationships as follows:
BridgeTable[Sprint] to SprintDates[Sprint]
BridgeTable[Sprint] to table1[Sprint]
BridgeTable[Sprint] to table2[SprintRelated]
Ensure that the cross-filter direction is set to single for these relationships to avoid circular dependencies.

Adjust Your Slicer:
Use the Sprint column from the BridgeTable in your slicer. This way, the slicer will filter all related tables without causing a circular dependency.

Here’s a simplified example of how you can create and use a bridge table in DAX:

BridgeTable = DISTINCT(UNION(SELECTCOLUMNS(SprintDates, "Sprint", SprintDates[Sprint]), SELECTCOLUMNS(table1, "Sprint", table1[Sprint])))

Best Regards
Saud Ansari
If this post helps, please Accept it as a Solution to help other members find it. I appreciate your Kudos!

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.

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.

ok,, so it kinda works.

I have the following tables:

1) BridgePIandSprint which has the PI and Sprint together as a "combokey"

2) BridgePITable(it is a child table to BridgePIAndSprint) and has a relationship based on PI

3) TimeInBacklogStatus which has the PI and Sprint together as a "combokey"

4) TimeInReady which has the PI and Sprint together as a "combokey"

5) I was able to establish a relationship between BridgePIandSprint and both TimeInBacklogStatus and TimeInReady

6) BridgeTeamAndArt which has the Team and ART together as a "combokey"

7) TimeInBacklogStatus which has the Team and ART together as a "combokey"

😎 TimeInReady which has the Team and ART together as a "combokey"

9) I was able to establish a relationship between BridgeTeamAndArt and TimeInBacklogStatus, however when I tried to establish the relationship between BridgeTeamAndArt and TimeInReady, I get:

"There are ambiguous paths between BridgePITable and BridgeTeam"

"BridgePITable->BridgePIAndSprintTable-TimeInBacklog->BridgeTeamAndARTTable-->BridgeTeam"

"BridgePITable->BridgePIAndSprintTable-TimeinReady->BridgeTeamAndARTTable-->BridgeTeam"

Not sure how to resolve this ?