Forum Discussion

PVO3's avatar
PVO3
Icon for Impactful Individual rankImpactful Individual
3 years ago

ISFILTERED between slicer

Hello,

 

Am I correct that the ISFILTERED function has changed lately?

Before, when using a between filter in combination with a between slicer, the function behaves as expected.

Today I noticed that when appling a filter on a between slicer and then removing this filter on the same slicer, the function still returns TRUE.

 

Example screenshot. Date ranges between 5-1-2022 & 2-12-2022 without filters (date all selected).

Removing the between slicers fixes this.

 

 

General Comment
Need Help

5 Replies

  • lbendlin's avatar
    lbendlin
    Icon for Super User rankSuper User
    3 years ago

    please provide a sample pbix that illustrates the issue.

  • PVO3's avatar
    PVO3
    Icon for Impactful Individual rankImpactful Individual
    3 years ago

    Ofcourse. 

    Once you apply a filter by using the between slicer, ISFILTERED correctly returns TRUE. But, if you try to remove the filter, by changing the slicer parameter, ISFILTERED still returns TRUE.

    • lbendlin's avatar
      lbendlin
      Icon for Super User rankSuper User
      3 years ago

      PVO3  I see slightly different but equally weird behavior.

       

      Original situation:

      Moved the date slicer in 

      Moved the date slicer back out

      Hit the "Erase" button on the slicer

      You would have to compare FILTERS() to VALUES() to catch the "everything" scenario reliably. Or raise a bug report.

      On the other hand you could use this quirk to distinguish between a "pristine" filter that hasn't been messed with yet, and a filter that was changed (and then changed back) by the user.

       

      By the way, the issue is not present when you use the filter pane instead.

      • PVO3's avatar
        PVO3
        Icon for Impactful Individual rankImpactful Individual
        3 years ago

        Thanks lbendlin.

        Since this occured in a recent version of PowerBI, I assume this is a bug. Not sure which exact version to be honest. A workaround is easy, but ofcourse not desired.