Hello,
I'm encountering an issue where visuals in my report crash whenever I apply a date filter. To isolate the problem, I tested it in a new blank report with just a simple table visual (containing one column) and a slicer using a date field. As soon as I use the date filter, the table visual fails to render and displays the following error: An unexpected error occurred (file "", line, function "").
This seems to happen consistently. Could someone please advise or help troubleshoot this issue?
Thank you!
6 Comments
- I have the same issue when basic filtering works but advanced or relative date fails. It seems like a huge bug in the new Power BI Desktop,.
- Are you using ARM64 in either Windows (Snapdragon) or Mac/VM? If so please see this thread which includes instructions to downgrade to the Feb Power BI Desktop release - https://community.fabric.microsoft.com/t5/Issues/March-2025-Update-Error-fetching-data-for-this-visual/idi-p/4633481#comments And then hop on over to this thread to upvote ARM64 official support, because at present Microsoft have said ARM64 is officially not supported. https://community.fabric.microsoft.com/t5/Fabric-Ideas/Make-power-BI-desktop-fully-compatible-with-ARM-CPU-such-as/idi-p/4681097#M160671
- I encountered the same issue with the Power BI Desktop May 2025 version while running it on a Mac using Parallels. However, I discovered that the problem occurs when using measures that contain IF or SWITCH statements. As a workaround, I was able to rewrite these measures using a DIVIDE(expression, if valid then 1 else 0) strategy. I hope this helps you overcome the issue and assists v-venuppu Microsoft in gaining a better understanding of its root cause. BTW: I still find it surprising that the issue does not occur on an Intel-based machine. Best regards, Frank van Zuilen, Pilares
- Hello everyone, I found a solution to my issue, and it might help some of you as well. I'm using a Mac and had installed Power BI from the Microsoft Store via Parallels. However, this version auto-updates to the latest release, which isn't fully compatible with ARM64. @Stinky's answer turned out to be the fix. Unfortunately, I can't mark it as the accepted solution or reply directly to the post, so I'm sharing it here instead. Hope this helps!
- It's more of a band aid that will unfortunately get worse the older it gets. I am optimistic that a future update to prism will fix it.
- I had the same issue running in HyperV - to solve it - uncheck the Compatibility setting in the properties of the VM. I am guessing this has something with a different (limited) instruction set. I thought of doing 5this after seeing issues people post with it not working on ARM machines.
