Forum Discussion
Helper IICircular Dependency Reference around Date[Date] in Service but not Desktop
Hi,
Something must have changed in the power bi service recently because I have not made any changes to the report for sometime and all the sudden the refresh schedule is failing with the following ambiguous message:
A circular dependency was detected: Date[Date], 2d8d683e-9123-4036-a9ec-837e6e42608b, Date[Date], Date[Date].
When I refresh the same report in Desktop it works without any issues and like I said I have not made any changes before that started to happen. The refresh schedule started to fail since yesterday. Before yesterday the refresh worked without any issues.
Microsoft Please Advise!
Thanks
Saner
Hi, alisaleh
The issue has been resolved and you can view the changes in the Power BI service.
Best Regards
Jianpeng Li
28 Replies
- GilbertQ
Super User
Hi AndrejZitnay
This is the reason for things breaking Troubleshoot refresh scenarios - Power BI | Microsoft Learn
I do believe a fix is being rolled out but could take a few days.
rbustamanteHelper I
Hello I have the same issue and after review all the 1:1 relation ships and change 1:any all works fine.
I don't know the reason because on the desktop works fine until last sunday.
Try this workaround and tell me please.
Ever since the weekend, every report of mine has failed because of this reason. I've tried every which way to find a work-around. I finally tried your method, and IT WORKED!
(Once again - the SOLUTION!)
For ALL calendar table related joins, you MUST change all the 1-on-1 joins to 1-to-many (and make it single, not both ways).
- alisaleh
That did not work in my case. It broke something else. The work around are appreciated and might help some poeple but this appears to be a Microsoft Bug. Needs to be treated and fixed as such. If there is anything we can do to bring this to Microsoft attention sooner please let us know. It seems many people have been affected by this.
Hey that's really work for me! Thanks!!! At least in 1 report it works fine
- alisaleh
Hi Ibendlin,
Thanks for your quick response. I like very straight forward response but the change you are asking seems a bit broad, dont you think?! Im concerned doing so might cause other issues specially when Im using auto generated Date\Time table.
Can you please provide some conectext on this and why do I need to do this now vs not before?
Where do I disable this feature?
Thanks
- lbendlin
Auto Date/Time is generally more harmful than helpful as it can result in gigantic extra storage requirements, especially if you have unclean dates like "12/31/9999".
Use a proper calendar table and let the visuals take care of the hierarchies.
You disable it in the "Options and Settings" dialog.
- lbendlin
Disable Auto Date/Time. Republish.
- AndrejZitnay
Post Patron
I have same issue from this Saturday.
Disable Auto Date/Time didn't helped. I have one PBIX wihtout Disable Auto Date/Time and have same issue.Same. 2/15 reports are broken now. One of them w/o auto date time now. And I got rid of the calendarauto(). Didnt help
I am having the same issue in at least 4 reports. It was working fine until two days ago and works fine in desktop. Please help
- alisaleh
I have not resolved that yest Im waiting on some one to help. Hopefully Microsoft figures out what they broke and fix it......and maybe do more testing next time before releasing changes.
- lbendlin
Did it work before 10/5 and stop after?
it was working for months and started receiving errors on oct 9th.
I do have date tables and had auto date/time disabled. I have been turning it on and off, unmarked date table, changed name, turned cache on/off, removed a day group from this table, nothing has worked until know.
I'm experiencing the same issue with four of my reports. They were working well until yesterday, even though I didn't make any changes. I've tried disabling auto date/time and republished yet it still did not work. Does anyone know the solution for this?
TesteriSame problem here. Started this morning. Worked fine until now. Auto date/time is not enabled in the data load options. Help would be appreciated.
- Testeri
I changed temporarily calendarauto -> calendar and refresh is working from the service. Hoping fix soon because calendarauto would be so much better in my case.
- AndrejZitnay
We have this problem on all reports with aggregate tables. Not just data tables. We use aggegated tables on few other variables.
Thanks to Tester, rbustamante, wwolfg
Hi, alisaleh
This issue is currently being processed and I believe it will be back to work soon. Please be patient and wait for it.
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, alisaleh
The issue has been resolved and you can view the changes in the Power BI service.
Best Regards
Jianpeng Li
Hi,
I am also facing the same type of error: "a circular dependency was detected: Data[Date], ba1c366-02d4-eaa5-932e-39d5a755d3ea, Data[Date], Date[Date]." in reports that were working correctly until a few days ago. Now, I can't make any changes to them because I keep getting "Circular Dependency" warnings. I am using the latest version of Power BI Desktop: Version 2.138.1004.0 64-bit (November 2024).- lbendlin
That's not the latest version. Try the new one
