If your application is already live, do not change label, because it misleads existing data. Also do not change value, that will mess the data.
There are two ways to fix this problem. You can choose whichever comfortable with you.
1. Adding new options to existing field
A. Add new optionset values and labels to existing field and patch this optionset field data to new labels
Example, add suffix <old> to all the existing labels, and add new labels and values. Then patch data from old to new values. Rename existing 'Resolve' label to 'Resolve <old>' then patch data from 'Resolve <old>' to 'Resolve'.
B. Look for the components (workflows, reports, plug-ins, javascript..) dependent on this optionset field and fix them with respect to new values added.
C. Delete the old optionset values. Need to manually delete the old optionset values from all the environments.
2. Creating new optionset field
A. Create new optionset field with corrected value and label mappings
B. Patch data in newly created optionset field from existing field
C. Check if there are any dependencies on old optionset field (like charts, views, workflows) and replace with new field and values
D. Check the source code (plugin, custom workflows, JavaScript, reports and other integrations) for old field dependencies and replace with new field and values
- Charan
Please mark as verified if the answer is useful.
