Forum Discussion
Strange Circular Dependency issue
So I'm trying to account for the error in package size maintained by us, versus the resellers.
My expression:
hi, DouweMeer
It is not a bugger, it is a common problem between calculate column and relationship
https://www.sqlbi.com/articles/understanding-circular-dependencies/
https://www.sqlbi.com/articles/avoiding-circular-dependency-errors-in-dax/
You can upload sample pbix file and expected output to OneDrive and post the link here. Do mask sensitive data before uploading.
Best Regards,
Lin
6 Replies
- v-lili6-msft
Community Support
HI, DouweMeer
For this error, it must be that one of 'ALL PRODUCTS'[Pieces/case], 'EMEA - Standard_1'[Selling Price], 'EMEA - Standard_1'[List Price] or 'EMEA - Standard_1'[Adjusted Cost] is calculate column and it is calculated based on anther table.
So just adjust it in the formula.
If you still have the problem, please share a simple sample pbix file.
Best Regards,
Lin
- DouweMeer
Impactful Individual
I understand your theory as I was looking for that as well. But those fields are not calculated.
Before this case, I also had the same issue with another expression:
lookupvalue ( all products [piece/case] , all product [item] , 'emea...' [product] )
where it would hit me with a circular dependency. I can't imagine a way where you can be hit a circular dependency when using a lookupvalue on a newly created calculated column.
I fixed the previous circular dependency by creating a dynamic table and using that dynamic table to do a:
sum ( dynamic table , value( dynamic table [piece price] )
To me, it tastes like a bug. Think I'm going to do the dynamic table trick again to fix this crap.
- v-lili6-msft
Community Support
hi, DouweMeer
Could you please share a simple sample pbix file for us to have a test :smileyhappy:
Best Regards,
Lin