Circular Dependency Refresh Error in Service but not Desktop

Question

I suddenly started receiving a circular dependency refresh error on a semantic model in service after never having the issue before and without making any recent changes to the model. When I download the pbix file there is no circular dependency error to be found and the file is able to refresh data successfully. Has anybody had this issue before and/or know of a fix?

For reference this is the refresh error:

Hide

On demand

1/31/2024, 11:25:52 AM

1/31/2024, 11:25:55 AM

Failed

There was an error when processing the data in the dataset.

Data source error:	A circular dependency was detected: Weekly Demonstrated Capacity (Dyeing)[Weekly Demonstrated Capacity (Dyeing)-d24b1c29-b175-4b88-95d8-0a1681a31bff], 12 Week Production (Dyeing)[Dye Line], 12 Week Production (Dyeing)[12 Week Production (Dyeing)-765b30db-120f-47ec-971e-a0d304a5ff29], d9b75eba-15a2-4009-88f0-5641aff4606b, Weekly Demonstrated Capacity (Dyeing)[WeekEnd], Weekly Demonstrated Capacity (Dyeing)[Weekly Demonstrated Capacity (Dyeing)-d24b1c29-b175-4b88-95d8-0a1681a31bff].

aj1973 · Answer

Hi&nbsp;alex_k&nbsp;It could be a DAX measure that is causing the circular dependency and is detected by the Service and not the Desktop.Avoiding circular dependency errors in DAX - SQLBI&nbsp;

Forum Discussion

Circular Dependency Refresh Error in Service but not Desktop

1 Reply

Related content

Circular dependency

Circular Dependency

DAX Help - Circular Dependency

Circular Dependency Error

A Circular Dependency was detected