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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
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 😞
Regards,
Surya
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!!!>
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.
Hi @karljackson
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.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.