Unable to execute DAX, A circular dependency was detected, using CALENDARAUTO()，PowerBI WEB works

[NiYH]

Upgraded the PBI desktop to Version: 2.138.782.0 64-bit (November 2024). 

When I open one of my PowerBI desktop file, get the following error message and can't refresh it. 

This deskotp file worked well in the old PowerBI version unitl I upgraded the PBI desktop to verion November 2024.

PowerBI server works well, I can refresh and get the latest data.

[WhyPBI]

This is embarrassing that Microsoft breaks something in the web service. Fixes it in the webservice, then breaks in in the desktop version. This issue has now been going on for months and no word from Microsoft on a potential solution. 

[Syndicate_Admin]

Hello, I have the same problem for several days, do you know how it has been solved?

[NiYH]

Not yet.

Temporarily change the `Calendarauto()` function to:

CALENDAR(

       DATE(2020,1,1),

       EOMONTH(TODAY(),3))

```

Then manually update the impacted visuals.

[Syndicate_Admin]

hello good evening, how do you update the PowerBI Server?
THANK YOU IN ADVANCE.

[NiYH]

Hello, this issue only impact the PowerBI desktop file. PBI service works well.  But I remembered that the PBI service had the same issues in last month.

[Ritaf1983]

Hi @NiYH 

There’s already a reported issue regarding CALENDARAUTO() and circular dependencies in the November 2024 Power BI update. Please vote for it here / add some details :
https://community.fabric.microsoft.com/t5/Issues/Problem-with-November-2024-update-for-PowerBI-Repor...

However, based on the images you’ve shared, there might also be an underlying design issue in your model that’s causing the circular dependency. This can happen if there are multiple relationships or dependencies between your Dim_Date table and other tables that unintentionally create a loop.

Suggested Steps:
Switch from CALENDARAUTO(): Instead of relying on CALENDARAUTO(), try creating a calendar table manually using either:

DAX:
DAX
Calendar = CALENDAR(DATE(2020,1,1), TODAY())
Power Query: Import a date table or generate one dynamically in the query editor.
This will give you more control and eliminate potential issues caused by automatic column detection in CALENDARAUTO().

Check Relationships: Carefully review all relationships involving your Dim_Date table to ensure there are no unintended circular dependencies.

Report the Issue: If switching to a manual calendar table resolves your issue, this could indicate that CALENDARAUTO() in the latest update is problematic for certain models. Consider commenting or adding details to the linked issue report above.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.