I have field1, field2, field3, calcfield1, calcfield2, complexCalcField1
Calcfield1, Calcfield2 uses field1, field2 and field3 for its values. ComplexCalcField1 uses Calcfield1 and Calcfield2 for its value.
Yes, whole calcfield1 and calcfield2 in complexcalcfield1 can be replaced with whole formula that is used to create calcfield1 and calcfield2. But, this just makes complexcalcfield1 formula difficult to read and maintain. But using instead already precomputed calculated fields ie calcfield1 and calcfield2 in complexcalcfield2 makes formula easier to read and understand and maintain.
This so called nested calculated fields works fine in list fields. But when I try to use such complexcalcfield in Content type hub or in Site 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. But the actual order in which these formulas should be calculated is first calculate calcfield1/calcfield2 and then go to calculate complexcalcfield1. But if the order is reverse ie trying to first calculate complexcalcfield1 before calculating calcfield1/calcfield2 will lead to error.
Have you had such problem before ? Is thery any solution for this.