Forum Discussion
Error: circular dependency
- 10 years ago
I assume these are calc columns, is that correct? I am aware of a circular dependency "issue" when you write multiple calc columns, and their incrementally refer to all columns in a table. It is very complex and I don't think I can explain it based on what I see. But my suggestion is that you don't write calc columns at all, but instead write measures. Read my article about the difference here. http://exceleratorbi.com.au/calculated-columns-vs-measures-dax/
I assume these are calc columns, is that correct? I am aware of a circular dependency "issue" when you write multiple calc columns, and their incrementally refer to all columns in a table. It is very complex and I don't think I can explain it based on what I see. But my suggestion is that you don't write calc columns at all, but instead write measures. Read my article about the difference here. http://exceleratorbi.com.au/calculated-columns-vs-measures-dax/
Hi Matt
Appreciate this is an old thread however I am facing the same issue - I am trying to calculate the maximum date in another table (that has been linked by a unique ID) - specifically, I have a table of Material Requests and a table of Purchase Orders - I want to know when was the last date that a Purchase Order was raised against this particular Material Request.
The formula I am trying to use is as follows:
Column = CALCULATE(MAX(PO[PO Date]),FILTER(PO,PO[UID]=EARLIER(MR[UID]))
this is giving me a circular dependancy error. I have tried taking your advice and using a measure but (at least at the auto complete level), this does not allow me to compare the UID in the PO table to the UID in the MR table.
I hope this is clear - any guidance or advice would be hugely appreciated.
Gratefully,
Tim