Forum Discussion
Advocate IMeasure Column in Table Visual Causes Filters to be Ignored
Ceeeg I can try to explain but I know why it is not working. This is why star schema is the recommended/best practice. To visualize the issue, in a table visual where you have store and sales with zero measure, add store type from the store type table, now filter on Fashion and you expect to see two stores (A and B) but you will see other stores as well showing for the selected type even though those stores are not associated with type fashion and the reason for that is we are forcing to add zero to the measure. So this is the main explanation why you see all the stores.
To overcome the best practice is to use star schema and/or update your measure something like this:
Sales Plus Zero = VAR __ForceZero = IF ( NOT ISBLANK ( SELECTEDVALUE ( Stores[Store Name] ) ), 0 ) RETURN Sum('Sales'[Value]) + __ForceZeroI hope it makes sense. Great question though.
✨ Follow us on LinkedIn and to our YouTube channel
I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make effort to give Kudos to whoever helped to solve your problem. It is a token of appreciation!
⚡ Visit us at https://perytus.com, your one-stop shop for Power BI-related projects/training/consultancy.
Advocate IUpdate:
I created a new measure in the measure table:
store_name =
MAX(Stores[Store Name])I added this measure as a filter to the table visual that wasn't filtering as expected, and set it to 'is not blank'. After doing this, filtering on the Store Type Reference table seems to work as expected.
Not really sure why this works, and not a practical solution in my situaton (I need to use the Sales measure against multiple dimensions, so I'd have to make a measure for each dimension, and at that point I may as well just make a calculated column), but I thought it might be a useful clue for someone more knowledgeable than me.
Community SupportHi Ceeeg
I am so glad to hear that your problem has been solved . Please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Yadong Fang
- Ceeeg
Unfortunately my update above isn't really a solution - at least not a practical one in my situaton - I need to use the Sales measure against multiple dimensions, and with this approach I'd have to make a measure for each dimension, so it'd be a fair bit of effort.
Cheers,
Calum
Have you found solution for that? And the reason of that behaviour? I have the same issue. Why does it work like that?
- Ceeeg
Hi Anonymous, while it's still not really intuitive behaviour, parry2k's explanation and solution are basically it - if you can manage to change your model from a snowflake schema to a star schema, it's going to fix the problem, and make things easier in general.
I recently did SQLBI's 'Mastering DAX' course, and I think after that, if I put my mind to it and had enough time, I might be able to fully understand why it doesn't work like we expect, and a workaround measure that does work. But if that's all you're after, it'd be a bit of an expensive answer for the question haha (the course is good if you're interested more generally though).