Forum Discussion
Is this a bug?
Thanks for the response. There definitely seems to be something to your explanation, as I can get around the issue by moving the MeasureColumn filter from the visual to a slicer. On the other hand, it also seems a bit more complicated, as the MeasureColumn 0 rows makes it to the DAX expression as long as the slicer filter doesn't completely reduce the dataset to 0 records...
Thanks for confirming that it is indeed weird. I will submit it as an issue 🙂
Yeah MrGorkajuice I think it is some kind of optimization going on with the Filter pane. It's similar if you have a Page level filter, those things will never be included in DAX calculations because they essentially get pre-filtered out before getting to DAX. The Filter pane can definitely cause weird behavior. But, I agree that it's odd because it only happens in this case when the set gets filtered to zero.