Weird behavior with date slicer and MAX measure on DimDate

[hectorlopezl]

Hey everyone, I'm running into some odd behavior in Power BI and wondering if anyone else has seen this.

Steps to reproduce:

1. Create a new report

2. Add a DimDate table using:

DimDate = CALENDAR( DATE(2024, 1, 1), TODAY() )

3. Add a slicer using the Date column from DimDate 

4. Create a measure

CurrentDate = MAX(DimDate[Date])

5. Add a card visual showing the CurrentDate measure

At first, everything works perfectly.

If I adjust the upper bound of the slicer, the card updates correctly.

But when I adjust the lower bound of the slicer (to move the start date forward), the card breaks and gives the "See details" error: "Error fetching data for this visual" "An unexpected error occurred (file '', line , function '')"

Now, if I change the measure to:

CurrentDate = MAX(DimDate[Date].[Date])

it doesn't show an error, but it shows the wrong date

Why would simply adjusting the lower bound of the slicer cause this issue? And why does it work with .[Date]?

The weirdest part is that this was working fine two weeks ago. This is a report I built for a client and it works on his machine.

I'm running Power BI on Parallels on an M1 MacBook. I've used it for a while and I haven't had any erros like this before

This is the error I got in the original report

[Derbenevigor]

Hello everyone. I solved this problem on my microsoft surface laptop 7. I need to configure prism, to do this, I need to find powerbidesctop.exe . I have it on this path. C:\Program Files\WindowsApps\Microsoft.MicrosoftPowerBIDesktop_2.143.878.0_x64__8wekyb3d8bbwe\bin . You need to select properties, go to compatibility settings, and select the emulation mode setting at the bottom. And turn on the safe emulation mode there. After that, the problem was solved.

UPD:

Yes, my solution is not fully working. older reports still have this problem. Apparently you need to wait for an update

[ElaineK]

Thakns for the suggestion - I am using a Surface laptop 7 too and was so hopeful that this would solve the issue for me too, but alas the same error persists:

[pcab8811]

same issue on Arm Surface Pro 11 with PowerBI x64.  However, when I installed PowerBI x32, the issue is not in the x32 version.

[ElaineK]

Is this bug being actively looked at? I downloaded the latest version this morning (Version: 2.142.1277.0 64-bit (April 2025)) and this error is still appearing across all dashboards that have a date based slicer. The only way I can resolve is to downgrade to the February release but this is causing all sorts of conflicts when opening files that other colleagues with later releases have worked on.

[pcab8811]

The PowerBI x32 version does not have the issue.  So how about just use the x32 version?

[apmulhearn]

@Rmateo1and @jemgrant73  I too am having this issue, and I did not previously.  I've had these same semantic models for about 4 years. 

I'm on an April 2025 version of Power BI and I'm using a Surface Laptop with ARM Processor. I've definitely been able to author in these reports since purchasing this computer. So maybe it is the recent updates? 

If I remove the date slicer, all is well. But I don't want to remove the date slicer.

[pcab8811]

The PowerBI x32 version does not have the issue on the Arm Surface.  Only the PowerBi x64 version has the issue.

[v-menakakota]

Hi @hectorlopezl ,

Thank you @Rmateo1  for providing information here,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.

[jemgrant73]

Hi There,

I'm having the same problem, however my slicers is linked directly to a date field in my table. This is not a new report and it has been working for over a year. As with @hectorlopezl , it looks fine until you adjust the slicer.

"Error fetching data for this visual" "An unexpected error occurred (file '', line , function '')"

Slicer is linked to the playback[Date] field.

Running PowerBi Desktop on Windows 11 - Version: 2.141.1253.0 64-bit (March 2025)

Appreciate any guidance!

[v-menakakota]

Hi @hectorlopezl ,

Thank you for reaching out to us on the Microsoft Fabric Community Forum.

It looks like you’re running into a filter context issue in Power BI, possibly made trickier by running it on Parallels on an M1 Mac (which isn’t officially supported). When you adjust the slicer’s lower bound, it might briefly leave no dates for the MAX(DimDate[Date]) measure to evaluate, causing the "Error fetching data" issue. The .Date syntax avoids the error by referencing a hierarchy, but it can pick the wrong date if the slicer’s filter isn’t applied correctly.

Since this worked before and still works on your client’s machine, it could be tied to a recent update or the Parallels setup.

Update your measure to handle empty contexts :

DAX

CollapseWrapCopy

CurrentDate = COALESCE(MAX(DimDate[Date]), "No Date Selected") 

This keeps the card from breaking and shows "No Date Selected" if no dates are available after filtering.

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

[hectorlopezl]

Hi @v-menakakota, thanks for your answer.

You suggested that

When you adjust the slicer’s lower bound, it might briefly leave no dates for the MAX(DimDate[Date]) measure to evaluate

Which is clearly not the case because how the DimDate table is defined:

DimDate = CALENDAR( DATE(2024, 1, 1), TODAY() )

Additionally, @jemgrant73 mentioned that he's experiencing the same issue on Windows 11, so it's not just a Parallels-specific problem

[v-menakakota]

Hi @hectorlopezl ,

Thank you for the clarification.

You’re absolutely correct , since your DimDate table is fully populated and the same issue occurs on Windows 11, this does not appear to be related to filter context gaps or Parallels.

Based on recent reports, this issue seems tied to the March 2025 release of Power BI Desktop (Version: 2.141.1253.0). Adjusting the lower bound of a date slicer may unexpectedly trigger a rendering error in visuals using measures like MAX(Date), even when valid data exists.

As a temporary workaround, we recommend updating your measure to handle potential blank values more gracefully:

CurrentDate = VAR _date = MAX(DimDate[Date]) RETURN IF(ISBLANK(_date), "No Date Selected", _date)

We appreciate you raising this and sharing the details.

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Thank you and Regards,

Menaka Kota.

[Rmateo1]

I'm having the same problem in the march 2025 version, did this workaround but still getting the same error. The only solution so far is using the "Before" style for the date slicer. I'm guessing this is a bug and should be resolved in a update.

[pcab8811]

Bug is still in the May 2025 version.  Issue with Before and Between setting of date slicer.  I'm using surface pro 11

[Rmateo1 · Accepted solution]

As a follow up to this post, I tested the same march 2025 version on a x64 backup laptop that I have and everything worked fine.

it seems the issue is with the ARM architecture, regardless if it's a Windows machine or running on Mac with parallels.

[pcab8811]

same issue on Arm Surface Pro 11 with PowerBI x64.  However, when I installed PowerBI x32, the issue is not in the x32 version.