Forum Discussion
ISINSCOPE messes up matrix
thescrimpton The answer to your first question is that ISINSCOPE just checks if the column is or is not in scope and returns true or false. Since you aren't aggregating any value, basically the filtering going on with the table relationships doesn't come into play when calculating this measure so you will always get back True or False and since you get a value back for each Product, then that row is displayed in your matrix. It would be the same thing as if you created a measure that returned a constant value.
Would need you to post sample data to mock this up. Good chance there is a different trick for this. One thing you might try is making your Product to Sales relationship bi-directional.
Community Championthescrimpton The answer to your first question is that ISINSCOPE just checks if the column is or is not in scope and returns true or false. Since you aren't aggregating any value, basically the filtering going on with the table relationships doesn't come into play when calculating this measure so you will always get back True or False and since you get a value back for each Product, then that row is displayed in your matrix. It would be the same thing as if you created a measure that returned a constant value.
Would need you to post sample data to mock this up. Good chance there is a different trick for this. One thing you might try is making your Product to Sales relationship bi-directional.
I didn't realize this is happening on the background until you add a measure. Thanks for the reply Greg_Deckler.
Since you aren't aggregating any value, basically the filtering going on with the table relationships doesn't come into play when calculating this measure so you will always get back True or False and since you get a value back for each Product, then that row is displayed in your matrix.