Forum Discussion
Circular dependency
- 3 years ago
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.
I have been running smooth for months and when I recently opened up a few of my PowerBi projects I am now getting an error I have never seen before. Nothing has changed with my projects and I am at a loss of where to search for the solution. Here is a screenshot of my error. Any direction would be helpful.
I am having this very same issue! Our keys are different, but he error is exactly the same! Did you find a fix?
- Anonymous1 year agoNot applicable
Yes I was able to find a work around for the issue. Instead of using "Calendar = Calendarauto()" I had to specify a date range for CalendarAuto to recognize. I switched it to "Calendar = Calendar(Date (2018,1,1), Date (2030,12,31)" and everything went back to working. This means instead of CalendarAuto seaching for its own range, you will be specifying the range in which the calendar table is limited to. Hope this helps!
- blat911 year agoNew Member
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!- sophiad07151 year agoNew Member
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