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"

EaglesTony's avatar
EaglesTony
Post Prodigy
1 year ago

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 ?

 

  • EaglesTony's avatar
    EaglesTony
    Post Prodigy
    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"