Forum Discussion
TREATAS returns blanks but USERELATIONSHIP returns values
First, the totals all being the same makes sense because, in the total line, there is no filtering happening related to territory. The filtering paths don't matter since they aren't being used.
Now, what's up with TREATAS? In this measure, the Doctors table is still filtering Visits but now you've added an additional filter on top of that. In particular, Visits is still limited to the rows that match the Doctors table (which is why you don't see the 1,266 in the blank row). If you insert ALL ( Doctors ) into the TREATAS measure, then it'll probably match the USERELATIONSHIP measure.
Super UserFirst, the totals all being the same makes sense because, in the total line, there is no filtering happening related to territory. The filtering paths don't matter since they aren't being used.
Now, what's up with TREATAS? In this measure, the Doctors table is still filtering Visits but now you've added an additional filter on top of that. In particular, Visits is still limited to the rows that match the Doctors table (which is why you don't see the 1,266 in the blank row). If you insert ALL ( Doctors ) into the TREATAS measure, then it'll probably match the USERELATIONSHIP measure.
Thanks Alexis!
I'd thought TREATAS would replace any existing filters and bypass existing relationships, but the ALL('Doctors') or REMOVEFILTERS('Doctors') does the trick 👍
