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! Get ahead of the game and start preparing now! Learn more
Trying to apply what I believe are "best practices", we have a DateDim table that ranges from 1900-01-01 until 9999-12-31. When I join my observation data set to the DateDim table and apply a slicer, the slicer range is from 1900-01-01 until 9999-12-31. In practice, my dataset starts from 2020-01-01 until yesterday.
What is the correct way to control this? In practice, the database uses 1900-01-01 as a NULL value, so limiting those observations out is not ideal. However, the slicer options are massive because of the range of the DateDim table. Any guidance on the best way to make it easier for the user?
@pbi_throw_away Two options. One, use the Date field from your fact table in your slicer. Second, create a column in your Date table like this and filter your slicer visual to 1:
Column =
VAR __Count - COUNTROWS(RELATED('Fact Table'))
VAR __Result = IF(__Count > 0, 1, 0)
RETURN
__Result
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 59 | |
| 46 | |
| 42 | |
| 23 | |
| 18 |
| User | Count |
|---|---|
| 193 | |
| 123 | |
| 99 | |
| 67 | |
| 49 |