Forum Discussion
Simple Relationship Understanding
I have heard about the issues with bidirectional. Great link though.
Please correct me if I'm wrong, but my understanding of bidrectional relationships is they cause trouble when you have multiple tables using them together (so as to create a multi path issue or circular relationship). Other than the inactive relationship (that I was forced to do), all of my tables are joined by a single relationship path directly to Project Summary.
I'm doing this so I can filter various data points for the same employee/project/day such as summing timesheet details and forecasted projects...
There is where I'm a little confused, forecasted Revenue should have a link (and only one link) to Projects[Stage] (through Project Summary). Is that not correct?!? DAX is saying it can't find the column at all without using that inactive relationship?!?!?
No, there are other probems with bi-directional relationships. Microsoft themselves recommend minimizing their usage. They impact the query performance as well. Best practice is, only use it if you know EXACTLY what you are doing and there is no other way. Same with many-to-many relationships.
As to your model, I cannot say for sure. I have seen weird things in models with bi-directional relationships that don't have ambiguity that suddenly work when you disable it. Had a user in here with a single bi-directional relationship that was causing a slicer issue. Turned it off and it worked fine. I'd go about removing all of those and then continue with your model building.