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!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Should a date slicer take note of page filters, or do they ignore page filters?
My date slicer is showing values of records that have been filtered OUT by a page filter.
I have a simple table as shown below.
| Code | Name | CreatedDate |
| A | AAAAAAA | 01-Jan-2022 |
| B | BBBBBBBB | 01-Jan-2023 |
I have a page filter to show Code=B only.
I have a TABLE visual on the page which correctly only shows 1 record.
However the date slicer shows 2022 and 2023 which makes me believe it is ignoring the page filter in place.
If I select 2022 nothing is shown in the table visual which is correct, but it is misleading to even see 2022 as an option in my date slicer.
Am I doing something wrong, or is it correct for the date slicer to ignore the page filter?
Solved! Go to Solution.
Hi @David_Morris ,
After my testing, I feel that you use the date hierarchy in your slicer, so the two years are preserved.
If you have a year column, such as a calculated column.
The Year column in the slicer can be filtered by the page-level filter.
This problem arises because of hierarchies, not slicers. As follows, if you put a single hierarchy of years into a table visual, two years also appear.
If the table visual has other fields, it is filtered due to the context of the row.
Therefore, it is recommended that you use a year column instead of a date hierarchy for the year.
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you for your detailed reply @Anonymous.
The slicer is indeed setup as a Date Hierarchy, and I confirm what you have explain to be the root cause of my issue.
If I set the slicer as a Drop Down list with the field set as the field itself (not a date hierarchy) then it honours the page level filters, however as soon as I change it to a date hierarchy, it is not honouring the page filter.
I have done as you suggested, and added a column to my data model to extract the YEAR our of the date field and added that to the slicer, and this is correctly honouring and looking at the page filters.
Thank you for putting me onto the appropriate solution. 😀
Hi @David_Morris ,
After my testing, I feel that you use the date hierarchy in your slicer, so the two years are preserved.
If you have a year column, such as a calculated column.
The Year column in the slicer can be filtered by the page-level filter.
This problem arises because of hierarchies, not slicers. As follows, if you put a single hierarchy of years into a table visual, two years also appear.
If the table visual has other fields, it is filtered due to the context of the row.
Therefore, it is recommended that you use a year column instead of a date hierarchy for the year.
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
You would have to show us your data model. The answer depends on where in the data model you took the columns from.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!