I have field1
, field2
, field3
, calcfield1
, calcfield2
, complexCalcField1
Calcfield1
and Calcfield2
use field1
, field2
and field3
for its values.
ComplexCalcField1
uses Calcfield1
and Calcfield2
for its value.
I know that calcfield1
and calcfield2
in complexcalcfield1
can be replaced with the formulas for calcfield1
and calcfield2
but this just makes complexcalcfield1
formula difficult to read and maintain. Instead using calculated fields, ie calcfield1
and calcfield2
, in 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, calcfield1
and calcfield2
are changed and replaced with #NAME?-#NAME?=
.
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 calcfield1
and calcfield2
. However, the actual order in which these formulas should be calculated is first to calculate calcfield1
and calcfield2
and then go to calculate complexcalcfield1
. But if the order is reverse as in trying to first calculate complexcalcfield1
before calculating calcfield1
calcfield2
then there will be an error.
Have you had such problem before? How can I solve this?