Circular dependency preventing scheduled refresh of data in Power BI service

[Bmann]

Hi, 

Never posted before but have a problem I can't get my head around... This morning I suddenly received failed to refresh notifications for many of our Power BI reports. The reports have been refreshing 3 times per day for several months without any issue until now.  

I have tried re-publishing the reports, sadly this did not help with the issue. The pbix files in the Power BI desktop refresh without any issues. 

The warning given states, "Something went wrong", "A circular dependency was detected..." 

The below post seems similar but does not have a clear solution, it appeared to resolve itself but I can't wait to see if that happens. 

Solved: Circular dependency in Service but not in Power BI... - Microsoft Fabric Community

UPDATE: Issue appears to be related to having a calculated table that uses the CALENDARAUTO DAX function

***UPDATE 18th OCTOBER***

The issue is now on the Microsoft Fabric support page and they're stating that it should be fixed by 20th October... No sign of it on the "known issues" section, but at least it looks like a resolution is due shortly.

link: Microsoft Fabric Support and Status | Microsoft Fabric

[scu_mitch]

Issue is still not fixed in current version. Using CALENDAR() as a workaround still works, but the underlying issue is still there, and not fixed since the October release. 

Version: 2.138.1452.0 64-bit (November 2024)

[PamMaca]

My Calendarauto is not working again, this was from 17th Dec.  Has there been another update?  (In Australia).  Is there a simple work around?

[Happydog1]

I can confirm it is NOT fixed my version of the Nov 2024 of PBI Desktop for Cloud (Ver 2.138.782.0 64-bit).  It was not an issue in PBI Desktop release from March 2024.  For now, it appears that the work-around suggestion of changing usage from CALENDARAUTO() to CALENDAR (start_date, end_date) works and avoids the issue.  

[rren]

Yeah same issue is coming back again, it happened before in the service but this time in the PBI Desktop (Version: 2.138.1004.0 32-bit (November 2024)). Please could Microsoft look into this and have it fixed soon.

[SBLI]

Hello, While waiting for Power Bi to correct your problem, I advise you to simply return to a later version (October).

https://power-bi-desktop.fr.uptodown.com/windows/versions

[ChaosDivergence]

Still happening in UK. I will see if I can raise a ticket.

[ArielAcosta]

Same here. After Nov'24 update I´m having this issue. Cannot change anything to try to fix the problem because turn any change back.

[MattHosk]

Also having this issue and I'm not able to change the relationship to One:Many due to the error. 

[AugustoNaga]

Hello, I think new versions of Power BI are not allowing to create a CalendarAuto with One:One relationship, when you try to refresh even locally it give you an error.
Instead try to use the relationship One:Many, selecting the CalendarAuto table as One.

At least in my reports this solved the problem since the update.

[xz2mo5]

@v-xingshen-msft 

[xz2mo5]

Experiencing the same here in Power BI desktop when trying to refresh, though not had this before! Previously only had this issue in Power BI Service semantic models. Also in the UK.

[peterps]

Same here.  I'd previously had issues with this in the semantic models for a few reports which I'd changed to CALENDAR from CALENDARAUTO.  This morning when opening a report I have to manually refresh it warned about a circular dependency and I couldn't refresh until I'd converted it to CALENDAR.

[ChaosDivergence]

On one report I got away with changing the relationship from one to one to one to many. On another one I had to change from CALENDARAUT to CALENDAR(DATE, DATE). 

[PatSz]

Hi there. Seem to be fixed in SLOVAKIA for now.

[Bmann · Accepted solution]

It appears this issue has now been fixed by Microsoft, so I am marking it as resolved

[v-xingshen-msft]

Hi All,
Thank you for your continued interest!，
And @Bmann,Based on the current update, the fix is expected to be deployed on October 20, and using Calendar functions instead of CalendarAuto could be a temporary solution.

And it's been a while since I've heard back from you and I wanted to follow up. Is there a resolution to the problem you are currently experiencing. If the issue has been resolved, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Looking forward to your reply!

[KaRe1982]

I faced the same issue last week.
I had two tables with relationship type "1 to 1" (one being a calendar table that used the function. 

CALENDARAUTO).
It seems that it helped that I have changed the relationship type to "many to 1" (having 1 for the Calendar table).
From that moment the scheduled refresh are working again correctly.

[AugustoNaga]

It worked in my reports after this changes

[power_bi_meh]

The issue seems to be fixed as of today 21/10/2024 in the UK. Thanks everyone for the active support of this ticket.

[xz2mo5]

I'm in the UK and still experiencing the circular dependency error code.

Data source error: A circular dependency was detected: Date[Date-0e2c1368-897a-4de5-9b04-e0c24d86ac78], 9a78025d-cc0c-4b3e-9d3b-b58cb82b6552, Date[Date], Date[Date-0e2c1368-897a-4de5-9b04-e0c24d86ac78].
Cluster URI: WABI-NORTH-EUROPE-J-PRIMARY-redirect.analysis.windows.net
Time: 2024-10-21 09:22:06Z