Forum Discussion
Dates Between slicer default value to MAX date
- 8 months ago
If your Calendar table is built from MIN/MAX of the fact, then the slicer’s max is already aligned to your data, but Power BI does not provide a supported way to force a Between date slicer’s handles (From/To) to default to a relative range like 'MaxDate-1', 'MaxDate' each time a user opens the report. The Between slicer will default to the full available range unless the report is saved with a selection, and it won’t “recompute” that selection as “latest two days” on open.
I'd suggest using 'Relative Date' slicer set to “in the last 2 days” or “last 1 day” depending on inclusivity. This dynamically evaluates on open/refresh.
The Between slicer is by default initialized using the full date range available in your Calendar table (i.e., Min → Max date at the time of load).
If by “MAX date” you mean the latest date in your dataset, but your Calendar table extends beyond that (for example, future dates), and you expect the slicer to dynamically move to the latest available date after refresh in Power BI Service, this behavior is currently not supported. Please consider submitting or voting for it as an idea here - https://community.fabric.microsoft.com/t5/Fabric-Ideas/Date-Slicer-does-not-default-to-latest-date/idi-p/4492771
MasonMA No, myCalendar table doesn't extend beyond that.
I am creating Calendar table using MIN & MAX of the fact table.
The feature I want is, if I place a Dates Beween Slicer, you see two dates to select a range.
So, in the LHS, it should show MAX-1 and in RHS it should show MAX date
- MasonMA8 months ago
Super User
If your Calendar table is built from MIN/MAX of the fact, then the slicer’s max is already aligned to your data, but Power BI does not provide a supported way to force a Between date slicer’s handles (From/To) to default to a relative range like 'MaxDate-1', 'MaxDate' each time a user opens the report. The Between slicer will default to the full available range unless the report is saved with a selection, and it won’t “recompute” that selection as “latest two days” on open.
I'd suggest using 'Relative Date' slicer set to “in the last 2 days” or “last 1 day” depending on inclusivity. This dynamically evaluates on open/refresh.