Forum Discussion
Filter multiple measures using single date slicer
Hi avinash2807
Your model is (close to) AMBIGUOUS. Please watch/read this first: Bidirectional relationships and ambiguity in DAX - SQLBI
To make your model work you have to get rid of this ambiguity. Since you have not shown the measures, I assume that in the one that uses USERELATIONSHIP you do not disable the connection between Tickets and FiscalYearTable. So, you've got an ambiguous model in such a case because then there are 2 paths from FiscalYearTable to the TicketAction table and the engine must select one of them. Obviously, it selects the wrong one from your point of view. Therefore, you have to make sure that your measure disables the connection to Tickets via the directive CROSSFILTER (the first directive in your measure is USERELATIONSHIP) -> CROSSFILTER(..., ..., None).
By the way, please change the 1<->1 relationship between FiscalYearTable and Tickets to one-way only, from FiscalYearTable to Tickets. You should never have to use 1<->1 in your models. This almost means the design is flawed. If such a connection exists, it means you should consolidate the data on both ends into a single table.
Solution SageHi avinash2807
Your model is (close to) AMBIGUOUS. Please watch/read this first: Bidirectional relationships and ambiguity in DAX - SQLBI
To make your model work you have to get rid of this ambiguity. Since you have not shown the measures, I assume that in the one that uses USERELATIONSHIP you do not disable the connection between Tickets and FiscalYearTable. So, you've got an ambiguous model in such a case because then there are 2 paths from FiscalYearTable to the TicketAction table and the engine must select one of them. Obviously, it selects the wrong one from your point of view. Therefore, you have to make sure that your measure disables the connection to Tickets via the directive CROSSFILTER (the first directive in your measure is USERELATIONSHIP) -> CROSSFILTER(..., ..., None).
By the way, please change the 1<->1 relationship between FiscalYearTable and Tickets to one-way only, from FiscalYearTable to Tickets. You should never have to use 1<->1 in your models. This almost means the design is flawed. If such a connection exists, it means you should consolidate the data on both ends into a single table.