Forum Discussion
How to fix Circular reference in Data Relationship
- 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"
Not sure if this will work, as I have a slicer based off Sprint and the other based off PI and I need it both directions, so when I select either a Sprint or PI, it will filter my data correctly in both tables.
I'm wondering if I do what you say and put a combined key on the 1 bridge table, but also keep those 2 fields (Sprint and PI) seperate on the bridge table will solve my issue.
You can try it if it helps then good, otherwise we have other expert can review this further.
Best Regards
Saud Ansari
If this post helps, please Accept it as a Solution to help other members find it. I appreciate your Kudos!
- EaglesTony1 year agoPost Prodigy
I will try it and if it works, will post the solution here for others.
- Anonymous1 year agoNot applicable
Hi, EaglesTony
Thank you for your swift response. I look forward to your updates and hope that our assistance proves effective for you.Additionally, if you find our help beneficial, I would greatly appreciate it if you could accept saud968's response as the solution. This would significantly contribute to the growth of our community.
Thank you in advance for your consideration. Wishing you a wonderful day ahead!
Of course, if you have any new ideas, you are welcome to contact us.
Best Regards,
Leroy Lu