Forum Discussion
Page level Filter not working
The above page level filter is not sorting the correct results.
Please advise
Hi winters_c ,
Thank you for reaching out to the Microsoft Fabric Community. Also thank you Elena_Kalina for pointed out the common reasons this issue might happen like conflicting filters, hidden time values in the LossDate column, mismatched date formats, or filters that sit right at the edge of the date range.
To address your issue in more detail, first make sure that LossDate is part of an active relationship in your data model and properly linked to the visuals you're using. Also, check if any of your measures use functions like REMOVEFILTERS or ALL() these can override the filters you've applied on the page. Please confirm that you’re using the exact same LossDate column in both your visuals and the filter pane. If time values are causing trouble, try creating a date-only version using DATEVALUE([LossDate]). As a quick test, try filtering a small date range like just one week and see if the issue still happens. These steps should help you get your filters working correctly.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
7 Replies
cannot share this file. Restricted.
The page level filter is not rendereing the correct number of records
Hi winters_c
Check for Conflicting Filters. Verify if any visual-level filters or "Filters on all pages" are unintentionally overriding your date filter.
Time Component Handling
Your filter includes 10 AM timestamps, which may conflict with your data.
Recommendation: Remove time components by:
Creating a date-only column: Date = DATEVALUE([LossDate])
Using the filter without manual time entries.
Date Format Validation
Confirm your dataset’s LossDate format matches the filter’s MM/DD/YYYY expectation.
Quick Test: Add a table visual showing raw LossDate values to spot inconsistencies.
Boundary Testing
Test a narrower range (e.g., 1/1/2025–1/15/2025) to isolate edge-case issues.
Check if records on 4/1/2024 or 3/31/2025 are included/excluded as expected.
Hi winters_c ,
Thank you for reaching out to the Microsoft Fabric Community. Also thank you Elena_Kalina for pointed out the common reasons this issue might happen like conflicting filters, hidden time values in the LossDate column, mismatched date formats, or filters that sit right at the edge of the date range.
To address your issue in more detail, first make sure that LossDate is part of an active relationship in your data model and properly linked to the visuals you're using. Also, check if any of your measures use functions like REMOVEFILTERS or ALL() these can override the filters you've applied on the page. Please confirm that you’re using the exact same LossDate column in both your visuals and the filter pane. If time values are causing trouble, try creating a date-only version using DATEVALUE([LossDate]). As a quick test, try filtering a small date range like just one week and see if the issue still happens. These steps should help you get your filters working correctly.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Hi winters_c ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
Hi winters_c ,
I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further. Please let us know if there’s anything else we can do to help.
Thank you.
Hi winters_c ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
