Forum Discussion
Finding Slicer Min with Multiple Selections
Ultimately, I solved this by taking the table responsible for the slicer and offloading it into it's own table separate from the data getting filtered on. I was then able to run my min/max calculations on the offloaded table which was no longer being filtered down by my data as the relationship was 1 way from the offloaded table to the new table.
Hi v-lili6-msft Lin,
This works in a 1:1 relationship, it does not work in a 1:* relationship unfortunately. It throws an error saying the argument passed to the allexcept cannot be all the columns in the allexcept table. I added in additional columns and this made the error go away, however it's back to detecting the wrong max and min slicer selections.
Also, simply hiding the effect the slicer selection is having on the max and min is not an option as the calculation itself is merely an intermediary measure for other calculations. The number itself must be correct.
Does anyone have any ideas on how to get the max/min of a slicer selection irrespective of whether or not all items exist in both selections?
Ultimately, I solved this by taking the table responsible for the slicer and offloading it into it's own table separate from the data getting filtered on. I was then able to run my min/max calculations on the offloaded table which was no longer being filtered down by my data as the relationship was 1 way from the offloaded table to the new table.