Need suggestions in calculations field update

[SivaK1]

Hi Team,

I’m trying to update the logic of a calculated field, but I see that it is currently mapped to multiple objects (like Project and Issue). When I attempt to update the logic, I’m running into errors. After checking the documentation, I found that the recommended approach is to rename the existing field, create a new field, and then apply the updated logic there.

Could you please suggest what objects might be impacted by this change, and what key considerations I should keep in mind before proceeding?

Thanks in advance for your guidance!

[IvanBebek-iX]

Hi @SivaK1,

This could be because some of the fields you are using in calculation do not exist on either objects, you can always add additional if states if you are not utilizing this at the moment, something like 

IF($$OBJCODE="PROJ","Smth for Project",IF($$OBJCODE="OPTASK","Smth for Issue","Smth else"))

Is this something that could make it work, so you do not have to create separate fields and then maintain similar/same logic across fields?

Also there have been errors that we faced in the past where one calculated field was utilized on multiple custom forms, and to make it work we had to remove the field from one custom form, update the logic for the field on the first form and then add the same field/logic for the field on the second form, but this was only happening for calculated fields created with old custom form builder (2 years ago) newer ones did not have this issue, maybe also something to consider if you have similar case.

Best regards,
Ivan Bebek