Forum Discussion
Circular dependency
Hi Niraj_vora0106 ,
Circular dependencies occur when a calculation depends on itself, directly or indirectly. In Power BI, this can happen when you create a calculated column that refers to itself, or when you have multiple calculated columns that refer to each other.
To fix a circular dependency, you need to find the source of the circular reference and either remove it or redesign the calculation so that it does not depend on itself.
In your case, it looks like you are trying to create a calculated column that sums the values in the final[vol] column and then filters the result using allselected. However, it is not clear how this calculated column is related to the Total Vol-Scheme column you mentioned, or whether there is a circular reference between the two columns.
To troubleshoot this issue, you can try the following steps:
- Check the formula of the Total Vol-Scheme column to see if it refers to itself or to any other calculated columns. If it does, you will need to redesign the calculation so that it does not depend on itself.
- Check the formula of the calculated column that is giving you the error to see if it refers to itself or to any other calculated columns. If it does, you will need to redesign the calculation so that it does not depend on itself.
- If you are still unable to identify the source of the circular reference, you can try creating a new calculated column using a simplified version of the formula, such as = 1 + 1, to see if the error persists. This will help you determine whether the error is caused by the formula itself or by some other factor.
If the problem is still not resolved, please provide detailed error information and test data. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Yes this helped! It didn't solve my problem, but it's defintely helped me find the error at least.
I'm going to take a different approach and write a calendar table as a query instead.
Thanks for coming back to me!
Did you try any different approaches that worked? I have tried using that workaround of specifying the dates instead of using "Calendar = calendarauto()", but no luck! I'm not even able to delete any of my tables or formulas to start from scratch without getting the circular dependency error...I am at a loss right now
The only other solutions I read about that also seemed to work was the one mentioned previous to your question. Creating a calendar table through the power query, that might be an option work pursuing. Once I found the fix for me, I didn't dig any deeper. Wish I was better help with this.
Yes - writing a new query is working.
The downside is that I now have to reformat my reporting and point all dates referenced in measures, filters, visuals etc. to the new query. Far from ideal, but with month-end approaching I don't have a lot of choice.
I'm going to save this 'new' suite as new. Hopefully Microsoft will fix the issue and the 'old' version will continue to work fine.The most frustrating part was that I checked the literature published by Microsof; 'The definitive guide to DAX', and we were doing the right thing all along, so I don't know whats changed.