Date Slicer - automatic update to latest Date in Online Reports

[cn4422]

Hi,

I'm using a date slicer with a "between" date-setting. I have set the date for the report-page to YTD.

What I would like to accomplish is, that the date can be manually selected in the date slicer, but the end date should always be the preset to the last available date (as it is when you set it to "after" in the slicer settings) when the report is opened

(I have set up a daily update of the data-set).

I've already tried with measures in the date slicer, but it's simply not working.

In my example on the screenshot, when I open the online report, the date is set to 13.01.2026 even though the report has been updated and the last available date is the 14.01.2026.

Thx for your help! 😊

[cn4422 · Accepted solution]

Hi @pallavi_r ,

I checked the other thread, but as far as I could tell, it doesn’t fully address the solution I was looking for (Or I didn't get it 😀).

I therefore resorted to the following approach:

I implemented a second date slicer and set it to “after”. Then I created a toggle that switches between the two date slicers using bookmarks. This isn’t a perfect solution, since the date slicer set to “between” is still not being updated. However, when the report is opened, the “after” slicer is the default and always provides current dates. If someone needs to set the date manually, they can switch to the other slicer and select the date manually.

[v-tsaipranay]

Hi @cn4422 ,

Thank you for reaching out to the Microsoft Fabric Community Forum.

Could you please let us know if the issue has been resolved? I wanted to check if you had the opportunity to review the information provided by @pallavi_r and @cengizhanarslan . If you still require support, please let us know, we are happy to assist you.

Thank you.

[cn4422 · Accepted solution]

Hi @v-tsaipranay ,

thanks for your post - I actually resorted to a workaround with bookmarks that's doing the job. 😊

[pallavi_r]

Hi @cn4422 ,

Unfortunately slicers don’t auto-update/change to data refreshes or visual/page-level filters.
With a “Between” date slicer, Power BI treats both dates as fixed once they’re selected. So even after a refresh, the slicer won’t automatically move the end date to the latest available date.

That's a limitation now which cannot dynamically reset the end date of a “Between” slicer when the report opens. 

I had faced this requirement where I had to auto update the latest month and latest year in slicer dropdown everytime the report opens and not to show the pre-selected old month and year. There I had written a Dax measure to show the latest month and year. And the solution is explained here in this post - https://community.fabric.microsoft.com/t5/Desktop/How-to-make-slicer-default-showing-latest-month-as...

The labels “Current Month” and “Current Year” didn’t look clean or visually appealing in the UI.

Thanks,

Pallavi

[cn4422 · Accepted solution]

Hi @pallavi_r ,

I checked the other thread, but as far as I could tell, it doesn’t fully address the solution I was looking for (Or I didn't get it 😀).

I therefore resorted to the following approach:

I implemented a second date slicer and set it to “after”. Then I created a toggle that switches between the two date slicers using bookmarks. This isn’t a perfect solution, since the date slicer set to “between” is still not being updated. However, when the report is opened, the “after” slicer is the default and always provides current dates. If someone needs to set the date manually, they can switch to the other slicer and select the date manually.

[cengizhanarslan]

Power BI does not automatically move the end handle to the new max date. It will keep the last saved/last-used end date (and in the Service it can also be influenced by persistent filters / “remember my selections”).What you could to instead of using between slicer is:

• Use Relative date: is in this year (or is in the last … depending on your need)

• It will always evaluate at open time / refresh time (no “stuck” end date)

Downside: you lose the classic “two-handle” between UI.

[cn4422]

Hi @cengizhanarslan ,

thanks for your reply.

Yeah, I thought about that, but I would like to keep the flexibility...