Forum Discussion
USERELATIONSHIP does not override active relationship
These are not simple relationships. You have created an ambiguous path between the continent table and the sales table. There are 2 paths when you use USERELATIONSHIP, which should the model use? The documentation is referring to 2 relationships between the same tables. In your case you have relationships between different tables.
It seems to me that you have a conflict. The q is “is it employee location or sales location that determines continent?” If it can be both, then use 2 continent tables or columns. If only 1, then just use that and ignore the other.
These are not simple relationships. You have created an ambiguous path between the continent table and the sales table. There are 2 paths when you use USERELATIONSHIP, which should the model use? The documentation is referring to 2 relationships between the same tables. In your case you have relationships between different tables.
It seems to me that you have a conflict. The q is “is it employee location or sales location that determines continent?” If it can be both, then use 2 continent tables or columns. If only 1, then just use that and ignore the other.
Thanks Matt. The following was a key insight to me:
"The documentation is referring to 2 relationships between the same tables. In your case you have relationships between different tables. "
For the record, I eventually got around the ambiguity by not using a relationship at all. I learned that I could simply compare the two dimensions directly in the measure:
CALCULATE(sum(Sales[Amount]),ALL(Employees),Countries[Continent] in VALUES(Employees[Continent]))
