Slicer Filter Misbehaving

[WishAskedSooner]

Hi Experts!

I have a report with several slicers. Call them A, B, C, D, and E. I have a MEASURE that returns a value based on the user selections of slicers A thru E. Call this [MyMeasure].

I have another slicer . Call this F that displays a field from a table of integer values that range from 1 to 100.

I want to filter the values in Slicer F so that only those that are less than [MyMeasure] are shown. So, I built a second measure called [FilterVals].

FilterVals =

    VAR _Val = [MyMeasure]

    VAR _Under =

        IF(

            VALUES(  'dimSlicerTable'[Slicer_F_Values]  ) < _Val,

            1,

            0

        )

RETURN

    _Under

Then I load this measure into the Filter pane of the slicer and set the filter to IS 1.

For example, [MyMeasure] = 65. Thus, I want only the values 1 to 64 to show up in slicer F.

However, I am getting a weird result where the values 1 to 74 show up.

If I hard code the value 65 in my measure it works properly.

When I load a card with [MyMeasure] it displays 65.

Thus, I can't figure out why this isn't working properly.

Any ideas? TIA!

[WishAskedSooner · Accepted solution]

Hi @ajaybabuinturi,

Thank you so much for your quick reply! I tried using the above, but all it did was filter out every value for some reason.

But your suggestion gave me some ideas. I need to go through my Report more carefully and check the filter interactions. That is probably my problem.

[v-tsaipranay]

Hi @WishAskedSooner ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.

[WishAskedSooner · Accepted solution]

Sorry for the late response. It turns out my interactions were the problem. Once I went through each one I was able to resolve the error.

Regrettably, my report is dizzyingly complex. But, I am happy to report that it is working properly now.

[v-tsaipranay]

Hi @WishAskedSooner ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-tsaipranay]

Hi @WishAskedSooner ,

I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

Thank you.

[v-tsaipranay]

Hi @WishAskedSooner ,

Thank you for reaching out to the Microsoft Fabric Community Forum, and great to hear you're actively troubleshooting this.

The DAX shared by @ajaybabuinturi  is correct using REMOVEFILTERS('dimSlicerTable') ensures [MyMeasure] is evaluated independently of the slicer’s row context, which is essential in this scenario.

If applying this logic results in all values being filtered out, it's likely due to additional filter interactions within your report. We recommend checking whether slicers A–E or any page/report-level filters are indirectly impacting 'dimSlicerTable' or [MyMeasure].

Also, review your data model for any active relationships that could be contributing to this behavior. As a quick check, try placing [MyMeasure] in a card next to a table of 'dimSlicerTable'[Slicer_F_Values] to observe how the values interact across rows.

Hope this helps. Please reach out for further assistance.

Thank you.

[ajaybabuinturi]

Hi @WishAskedSooner,
Could you please try with below DAX 

FilterVals =
VAR _Val = CALCULATE([MyMeasure], REMOVEFILTERS('dimSlicerTable'))
Var Result = IF('dimSlicerTable'[Slicer_F_Values] < _Val, 1, 0)
RETURN
Result

Thanks,
If you found this solution helpful, please consider giving it a Like👍 and marking it as Accepted Solution✔. This helps improve visibility for others who may be encountering/facing same questions/issues.

[WishAskedSooner · Accepted solution]

Hi @ajaybabuinturi,

Thank you so much for your quick reply! I tried using the above, but all it did was filter out every value for some reason.

But your suggestion gave me some ideas. I need to go through my Report more carefully and check the filter interactions. That is probably my problem.