Ambiguous path fix for filtering when both paths are valid

[scottiamit]

One thing staff have raised is that in the filters they see information from the multiple companies even though they have chosen a company via a filter. Some of these I have solved by enabling the cross filter direction on the relationship to operate in both directions.

One issue I am not quite sure how to handle is in the case of the following relationships (image below). Currently the relationship from Branch to Company is enabled so if you are viewing sales and click on the Branch filter you only see a list of options restricted to the Company selected. However since the relationship from SalesPerson to Company is not active when you click on the SalesPerson filter currently you get a list of all options from all companies. If you scroll down the list and click the SalesPerson you want it does the filtering of Invoices/Sales etc as intended it is just messy for the end users.

These are both valid and one to one relationships, An Invoice can only have one SalesPerson and it can only have one Branch, each SalesPerson belongs to one Company and each Branch belongs to one Company.

We only use standard PowerBi filters (no slicers). I tried creating a measure using distinct and userelationship to get a list of valid salesPerson results that I could then add as a filter but this didn't work either.

I would appreciate some guidance. Thanks. 

[lbendlin]

Make both paths inactive and then in your measures use USERELATIONSHIP to activate the appropriate path.

[scottiamit]

Thanks but SalesPerson and Branch are standard tables with the actual persons name or branch name within the joined tables, they are not measures. They are also not visable on the Matrix anywhere I am wanting to use these fields as available filters (standard filters not slicers). I will revisit and see if I can do something with a measure to resolve this.  It would be good if you could apply the USERELATIONSHIP to a filter specifically to solve this. Thanks.

[lbendlin]

No, that's not possible unfortunately. Refactor your data model, or - worst case - use separate data models for the different business questions.