Circular dependency Unknown Table

[lovishsood1]

Hi Team,

Suddenly out of nowhere, I received this Circular Dependency error :

A circular dependency was detected: DateTable[DateTable], 84c529b2-492a-b469-6a9e-9782359dd997, DateTable[Date], DateTable[DateTable].

From past 2-3 months, Scheduler was working fine. Now , suddenly I'm getting this error and In POWER BI Desktop , Refresh is working fine.

Can anybody tell what exactly is the issue and How do I resolve it?

I have attached the Model view and Data for reference.

[lovishsood1 · Accepted solution]

Hey guys, 

I have resolved this issue by putting relationship of HolidayTable and DateTable to Inactive and used LookupValue function to fetch data from HolidayTable in DateTable.

"IsHoliday", IF(NOT(ISBLANK(LOOKUPVALUE('Holiday Table'[Date], 'Holiday Table'[Date], [Date]))), "True", "False")

[Anonymous]

Hi @lovishsood1 

This issue has been confirmed as a known issue internally. You can try change the CalendarAuto to Calendar function. If this workaround do not solve your problem, please be patient to wait for fixing. If there is any news, I will update it here.

Best Regards,

Jayleny

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

[lovishsood1]

I have not used the CalendarAuto function.

[Testeri]

If you are using calendarauto() in your datetable you may try changing it to calendar() as a workaround until fix. It worked in my case.

[rajendraongole1]

Hi @lovishsood1 -The error you're encountering in Power BI, related to circular dependency, typically happens when two or more calculated columns, measures, or relationships depend on each other, creating a loop in the data model. 

Check the relationships between your DateTable and other tables. Sometimes, multiple active relationships or bi-directional relationships between tables can inadvertently create circular logic. You may want to:
Ensure there is only one active relationship per dimension.
Use single-directional relationships where possible.
2. Calculated Columns and Measures
Review any calculated columns or measures in your model that may refer back to the DateTable. Circular dependencies often arise when one calculated column or measure relies on the output of another measure in a way that loops back to itself.
If you are using CALCULATE or FILTER with the DateTable, ensure they aren't indirectly creating loops.
3. Date Hierarchies
If you are using hierarchies (e.g., Year, Month, Day) in the DateTable, make sure the relationships between them are logical and do not involve mutual dependencies.
4. Change Relationships to Inactive
Consider making some relationships inactive where necessary. You can activate relationships on-demand within your DAX measures using the USERELATIONSHIP() function.

Please check on the above points and let see. 

[lovishsood1]

But I'm not receiving any error in Power BI Desktop only in Power BI service. Why is that?

[rajendraongole1]

Hi @lovishsood1 -Check if you're using incremental refresh in the Power BI Service. If so, try disabling it temporarily to see if the issue persists with a full refresh.Revisit the steps in Power Query that involve the DateTable and ensure there’s no inadvertent circular logic being introduced. check if there is any complex DAX measures, especially time-intelligence or cumulative calculations, as they might be evaluated differently in the service.

Simplify the Model: Try isolating different parts of the model or simplifying it temporarily to identify the source of the issue. For example, disconnect certain relationships and see if the problem persists in Power BI Service.