Circular dependency in Service but no issue in Desktop

[Mila123]

Hello,

I have two BI reports each having it's own dataset. Both were running for more then a year. Suddendly they stopped refreshing due to the same data source error: A circular dependency was detected: calendar[DATUM]...

When I refresh data in desktop and publish the report it works fine. I can even see published report. But when I want to refresh data in Service it fails. For test I've published a report dated in January 2024 and this one has the same refresh error. It looks like something has changed in Service. I'm so confused because of this discrepancy and don't know from where to start. I couldn't find anything similar in forums. My calendar is created with GENERATE( CALENDARAUTO()... Since there is no issue with calendar in Desktop I don't know why it fails in Service. Where or how should I dig to find the source of the error?

I would appreciate any hint or if someone had such issue what was the solution.

Regards, Mila

[lbendlin · Accepted solution]

Re: Circular Dependency Reference around Date[Date... - Microsoft Fabric Community

[allyklee · Accepted solution]

We had the same issue with calendarauto().  We replaced it with 

If you have one fact table you can also just use min/max transaction date instead of a hard coded start/end date like above.  

[Mila123]

@allyklee thank you. This is also a solution. Though it was not so easy to determine min date in our case where a lot of tables contain historical data.

Since the date field in our calendar table was renamed, the change AUTOCALENDAR to CALENDAR caused all relationships dissapeared. So in our case was better to change relationship 1:1 to 1:N.

[lbendlin · Accepted solution]

Re: Circular Dependency Reference around Date[Date... - Microsoft Fabric Community

[Mila123]

@lbendlin , thank you very much. Yes, the solution is change all 1:1 relationships to 1:n with single direction. My calendar was connected with monthly plan and holidays, both 1:1.