Forum Discussion
Slicer stopped working with between style
ok, I beleive I have managed to fix it myself, but it does appear to be a bug, so I'll explain it here in case it helps others
This is the direct query I use, the slicer is on event_time_rounded, but as you can see the query also has a predicate on waitstartdate and waitenddate, which are parameters
You can see that the default values for theses parameters are more than 60 days ago i.e 01/10/2025 and 10/10/2025 and because I keep a rolling 60 days of data, those values will filter out all rows.
However on the page itself, I have more recent dates linked to these parameters
But the silcer with 'between' seems to ignore these and instead validates on the default values i.e. it expects no rows
But the rows are there. You can see them If I change the slicer from 'between' to 'dropdown', it just doesn't show them when using 'between'
So the fix is the change the default values to something that does return rows
and then the slicer displays correctly with 'between'
Wierd bug
Roger
Hi roger-allen ,
Thanks for reaching out to the Microsoft fabric community forum.
The issue you're experiencing is due to a known limitation in Power BI when using DirectQuery with date slicers set to Between, Before, or After. These slicer options require Power BI to find the minimum and maximum dates at query time, but in some DirectQuery cases, it can't always resolve those values because of how queries are processed or how the data source applies filters.
As a result, the slicer may appear blank, even though the same field works in Tile or List mode. This isn't caused by the column data type, page or visual filters, or a problem with the report itself. It's also why you can't fully reproduce this in Import mode with DAX, since Import mode always knows the full date range. For a reliable solution, consider using a relative date slicer or importing a calendar table for date filtering.
Best Regards,
Tejaswi.
Community Support