Forum Discussion
Circular reference error detected after Upgrade to April 2024, but not after downgrade to March 2024
Super UserRefreshing all data sources made the error go away for me.
Thank you lbendlin for the reply.
Unfortunately, that did not work for me.
I did leave out a potentially crucial peice of information. Table1 is a calculated table generated via DAX.
Remaining Open Status Age =
SUMMARIZECOLUMNS(
'Products'[Name],
'Still Open'[Status],
'Still Open'[Days open],
'Still Open'[Has JIRA],
'Still Open'[Start of Month],
FILTER('Products', 'Products'[Name] <> BLANK()),
FILTER('Groups', 'Groups'[Team] = "Team A"),
"Remaining Open", COUNTROWS('Still Open')
)
I can refresh everything in Power Query ok. Since Table1 is generated by DAX, the opportunity to refresh the data only occurs with the refresh button in the Home ribbon menu. When I try the to refresh from the home menu button I get the Circular dependency error.
I also tried refreshing each table individually as well, but got the error saying that it detected the circular dependency on Table1. For example, I tried refreshing the Calendar table, which is imported from an excel file (not dependant on Table1 or any other data from the other tables in the pbix) and still got the Circular dependency error.
Any other thoughts?
I'm just perplexed that I can refresh it no problem in the March 2024 version, but not in the April 2024
- lbendlin
Microsoft gives no guarantee of backwards compatibility when they update the rendering engines across the service, desktop and gateway. One has to assume/hope that they improve the engine and reduce/remove errors. So potentially the prior behavior was due to a bug in the engine.
Of course there is also the possibility that they introduced new bugs. If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .