Changing the names affects some out of the box functionality of the system, as our R&D team discovered. I am not aware of the specifics as you requested, so I suggest you wait for Clarizen's input on this.
Changing the API name that is assigned to the field once the Field Name is created
I would like to know what will be affected if we change the API names of the fields. We have updated the Field labels so we want the API names to be the same as the Field labels. Kindly let us know the risks associated with doing this i.e. if workflows, custom actions or anything using these API names will be impacted, broken etc.
Please sign in to leave a comment.
Thank you Guy
Changing the API name will also break all workflow rules and other configurations that use that field. If you do change the API name, I would recommend doing a search for the old API name in the upper-right of the Configuration page to find all rules that use that field and update them. If you are using integrations, it may also break syncs between Clarizen and other systems.
Thank you Josh