field3 for its values.
Calcfield2 for its value.
I know that
complexcalcfield1 can be replaced with the formulas for
calcfield2 but this just makes
complexcalcfield1 formula difficult to read and maintain. Instead using calculated fields, ie
complexcalcfield1 makes the formula easier to read, understand, and maintain.
This so called nested calculated fields works fine in list fields. But when I try to use
complexcalcfield1 in a Content Type Hub or at the Site Collection level, it is saved, but later on when I see them,
calcfield2 are changed and replaced with
Does anyone have any idea why this does work in list level and not in Content Type Hub level or Site Collection level?
My guess is somehow for
complexcalcfield1 to know/calculate its value, it must know value for
calcfield2. However, the actual order in which these formulas should be calculated is first to calculate
calcfield2 and then go to calculate
complexcalcfield1. But if the order is reverse as in trying to first calculate
complexcalcfield1 before calculating
calcfield2 then there will be an error.
Have you had such problem before? How can I solve this?