Date Filter Error

[karljackson]

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 😞

[haputhanthree]

I encountered the same issue, but installing Insider Preview 27881.1000 resolved it for me.
Power BI Version: 2.144.1155.0 64-bit (June 2025)

[Versus]

The issue seems to be happening on ARM processors and relates to date fields. Even though they are data fields, they are processed as text, which is causing the issue (that's my assumption).

Date fields are not converted and this raises the error:

Companies2 (L28D) = 
CALCULATE(
    DISTINCTCOUNT(companies[id]),
    companies[created_at] >= TODAY() - 28 &&
    companies[created_at] < TODAY()
)

Here the dates are explicitly converted to dates and it works OK:

Companies (L28D) = 
CALCULATE(
    DISTINCTCOUNT(companies[id]),
    DATEVALUE(companies[created_at]) >= TODAY() - 28 &&
    DATEVALUE(companies[created_at]) < TODAY()
)

Unfortunately, there is no workaround for filters and visuals.  They display error anyway.

[Versus]

My PBIX fiel is from May version and it refuses to open in version Feb'25.

Is there a way to downgrade the file to Feb'25?

[karljackson]

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

[v-karpurapud]

Hi @karljackson 

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.

[karljackson]

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.

[jkbrookes47]

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.

[rs3782]

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.  

[jaap8]

The April 2025 update is out. I hoped the problem was fixed, but no.
Still no solution. I stick to the Frebruary 2025 version.

[philmenown]

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

[karljackson]

Wow thanks, I was going to look into this myself soon to review if it was fixed. I think not.

[msgracegong]

Hi Karli, thanks for raising this issue. Im a PM on the Power BI team supporting desktop and our team is in discussions internally to see if we can expand our support for the ARM scenario. If you have any more comments or details you would like to provide, feel free to add that in the support ticket or in this forum and our team will review. Best regards, Grace

[karljackson]

Hi @msgracegong I will try and get some more details for you.

Basically this is still going on.

I'm working with a 3rd party company who are rebuilding our suite of reports and they also come accross the same issue.

The issue doesn't persist in the cloud, so i feel we either stay with the Feb version (which a lot of people have) or simply build in the service?

I'll see if I can get any further examples for you though.

p.s. the top comment has a mark for a solution, how do i remove this as there is no solution yet as i know 🙂

[rs3782]

Any updates on a solution?  Been stuck on Feb 2025 version basically since March.  

[mathiasrh]

Same issue here!

[Shalaby]

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.

[kw6575]

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

[kylienorwood]

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. 

[rs3782]

Would really like the Microsoft team to work on this.  Has been a known issue since March 2025 and all the threads I can find on the topic have no real solution outside of reverting to Feb 2025 release.  I do think we (as a community) should stop marking things as solved when the only real solution is a work-around, not an actual fix. 

[Shalaby]

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.