Forum Discussion
Date Filter Error
I have recently updated the Power Bi desktop: March 2025 Update (2.141.1228.0)
But upon opening any file I get the following error:
This has never happened before and causing issues updating any reports, the error also isn't very helpful 😞
26 Replies
I have the same exact problem.
The behaviour I noticed is: When I control the end date, it is absolutely fine, but the issue appears only when I control the start date.
The error I see on the visual is: Error fetching data for this visual see details. and when I click on see details I find out a non-helpful message: An unexpected error occurred (file", line, function "). date filter
This is really annoying and caused my complete work to stop!!!>
Rolling back to the February 2025 Power BI Desktop version resolved 🚀 the issue.
This version can be found under the [Previous monthly updates to Power BI Desktop and the Power BI service] page
I also raised a ticket (#2504021420003948) with Microsoft, describing the problem. The support engineer kindly shared a page listing all previous Power BI versions. After installing the February 2025 version, the issue was resolved.
It appears to be a bug that Microsoft may need to address with a future fix.
Do we know if PBI is working on this? I don't see it listed in the known issues and I would like to be notified when it's resolved.
Regrettably, I don't know. However, I have initiated a ticket with Microsoft, and the initial troubleshooting step recommended by the support engineer was to install February 2025 version. This resolution proved effective for me.
Can I ask how you rolled back to the February version. I can not seem to locate a download file or find a way via Microsoft store to rollback.
Also, were you using a ARM processor? This problem only exists on my Surface with a Snapdragon processor.
Thanks for any assistance.
Keith
I have raised a ticket:
https://community.fabric.microsoft.com/t5/Issues/Fix-the-Date-function-in-DAX/idi-p/4710619
Please vote for it if you're having this issue.
retrospectively, if you see or know of a similar issue, please reference it 😀
https://community.fabric.microsoft.com/t5/Issues/Fix-the-Date-function-in-DAX/idi-p/4710619
Hi Anonymous
Thank you for the update. Since you have already submitted your idea, I have upvoted it as well. With increased visibility and community support, it has a better chance of being prioritized for review by the relevant product teams. Microsoft will continue to evaluate and enhance the platform to meet the stability and experience that users rightfully expect. Hope your issue gets resolved soon. When it does, please share the insights here and mark it or any other helpful answer 'Accept as Solution', which will help others with similar queries.
Thank you.
Hi Anonymous
Thank you for reaching out to the Microsoft Community Forum.
Since the issue started occurring after updating to Power BI Desktop March 2025 Update (2.141.1228.0) and affects all files, it is likely related to a bug in the latest update, corrupt installation, or conflict with existing dependencies and compatibility issues with existing datasets or custom visuals. It would be helpful to raise a support ticket with Microsoft for better assistance on this.
You can submit a ticket through the Microsoft Power BI Support Portal:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If my response has resolved your query, please mark it as the Accepted Solution to assist others. Additionally, a 'Kudos' would be appreciated if you found my response helpful.
Thak you.How can this issue be marked to have a solution? Should users keep reverting to Feb 25 version for ever?
I keep getting this error on almost all our reports, it's devastating.
The error comes even if there is NO DAX syntax but just from setting a date filter in the UI, filtering an object or a page.
My colleagues say we need to have another tool than Power Bi but I spent SO many hours developing all the reports... 😞
I agree - on all threads the Feb 2025 reversion is marked as a solution when it is not a viable long term solution.
Same issue here!
Oddly I totally forgot about this issue because i have refused to update my Power Bi Desktop since I raised this issue.
It wasn't until a colleague came and asked for my support regarding this issue today that i remembered this post ande come to check it out, figures that the issue is still persisting, i'll look into raising a support ticket, or backing up a current ticket.
I have the exact same issue with Version: 2.141.1253.0 64-bit (March 2025)
When I filter on a specific data range I get the error. When removing the date filter from the visual, the visual is working back again.
Anonymous ,
- Try the following troubleshooting steps:
- Refresh the dataset manually and review the refresh history for any errors.
- Make sure the dataset size does not exceed the 1 GB per dataset limit in Power BI Service.
- Create a new Power BI file, add the new visual, and publish it separately to test.
- If using a gateway, double-check the credentials and settings under Manage Gateway & Data Sources.
- Publish the report using latest version of Power BI Desktop and test again.
- If the issue persists, try replacing the new card visual with a standard card or KPI visual.This error will happen mostly using new card.
Regards,
Surya
All of these comments are spot on with an issue I am also having. It does seem specific to date filtered-affected Measures. Would be really nice to know if Microsoft is aware of and working on a solution. I use this specific file/report monthly and have used the same report with the same measures for over a year with no issues. After this update, multiple of my measures are broken with no syntax errors and no clear error message other than the "file, line function" message.
The April 2025 update is out. I hoped the problem was fixed, but no.
Still no solution. I stick to the Frebruary 2025 version.I just tried the May edition and issue still not fixed :(.
It seems to be if you're running an ARM chip and using any date DAX functions / filters.
Keeping to the February 2025 edition for now
I was able to narrow this down further
FILTER(
ALL(BREAKDOWN_HISTORY),
BREAKDOWN_HISTORY[Period Date] >= DATE(2024, 4, 1) &&
BREAKDOWN_HISTORY[Period Date] <= DATE(2024, 12, 31)
)but this works
FILTER(
ALL(BREAKDOWN_HISTORY),
BREAKDOWN_HISTORY[Period Date] <= DATE(2024, 12, 31) &&
BREAKDOWN_HISTORY[Period Date] >= DATE(2024, 4, 1)
)The issue is that BREAKDOWN_HISTORY[Period Date] >= DATE(2024, 4, 1) but the workaround is to have it after BREAKDOWN_HISTORY[Period Date] <= DATE(2024, 12, 31)
This doesn't help if you are trying to use the between slicer (as I am) but I found if I apply the "before" slicer and then apply the "after" slicer that it will work, although ugly as hell.
