Forum Discussion
Error: circular dependency
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, I have a similar problem to the original poster.
I would be happy to use a measure, as in the tabular view it gives me the result I need.
However, you can't use a sliding date slicer with measures, only columns. Any ideas?
Why can't you put the slicer on the date column in your calendar table?
I can in the first table, and it works.
But in another table, I'm trying to agregate by earliest date from the first table. This has been possible in the past if I merge the tables and then expand the date column by min only, but the refresh takes hours on millions of rows.
I was able to solve this before with the help in this thread, but now something has changed. Instead of building up the original zone table from some merges myself, an engineer created a view on the central database for me. I thought this would be better, but now the millions of rows problem has returned. So again I tried to use Calculate to solve it, like in that thread, but this time I'm getting the circular dependency error, which is new.