Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
I have a date table with dates that end at the end of the last finished month. I have a between slicer with a start and end date.
The table is filtered in Power Query, filtered on the visual, has a measure that show if the month is finished to use as a filter. All of them have been applied and work great if you open the calender (greyed out future dates). But when the user types in a data manually it does not verify if that date exists. It just selects it and ruins the data.
How do I prevent the user from entering a date in the future?
Solved! Go to Solution.
Hey @SvenV_98 ,
Its a glitch in the system. I think I went down a rabbit hole around one and a half year ago for this but long story short, Power BI will not stop the user from manually entering the future date. Internally though, it will take the maximum date in the date table allowed in the filter context (check by populating a card visual by dragging and dropping the date field and changing aggregation from earliest date to latest date). Since there was no workaround, I added a filter summary table in the report populating it with the actual end date that was being applied internally. So yeah, it is just a frustating limitation.
Hope it helps!
Hey @SvenV_98 ,
Its a glitch in the system. I think I went down a rabbit hole around one and a half year ago for this but long story short, Power BI will not stop the user from manually entering the future date. Internally though, it will take the maximum date in the date table allowed in the filter context (check by populating a card visual by dragging and dropping the date field and changing aggregation from earliest date to latest date). Since there was no workaround, I added a filter summary table in the report populating it with the actual end date that was being applied internally. So yeah, it is just a frustating limitation.
Hope it helps!
Thanks for the clear response. You are absolutly right. I've made some measures to verify that the future dates are not used. I've selected almost 3 years of dates, and it returned 23 full months, that matches the amount of months between 1-1-24 and 30-11-2025.
Unforunatly this does not work. It will for the calender selector, but not for the manual date entering:
Before entering the date manualy:
After entering the date manualy:
| User | Count |
|---|---|
| 56 | |
| 41 | |
| 38 | |
| 21 | |
| 21 |
| User | Count |
|---|---|
| 140 | |
| 102 | |
| 64 | |
| 36 | |
| 35 |