Hi all,

I assume it is not a good idea to base calculation fields on other calculations. Yet it seems like a lot of calculations need to be repeated if not.

Let's say a there is a calc field :Age (current year - birth year). If I needed to calculate years to retirement would I do the calculation from from the Age calc field or duplicate the age calc at the start of the Years to retirement calc field? I assume is a calculated field becomes highly breakable if based on another, but then again is it best that the age calculation only exist once and that calculations refer back to the logical field like the Age field. Are there performance implications?

I hope this makes sense. I probably should have had my head around this by now!

Hammeroz,

This is done all the time. While it's OK to do it for 1 or 2 layers deep on one or two calculations it is not a 'best practice'. Each layer adds a dependency to the calculation and requires each level to be calculated for every record. The number of computations increases dramatically after even a couple of layers.

At approximately 13 levels I found it almost unusable. Even a simple calculation like 14 day fields each subtracting from the previous one will become very slow.