Choice list option deletion is INSERT_OR_UPDATE change to sys_choice table in update set. Does this mean it will recreate deleted choices again if overwritten with a version of the choice list which does not have the choices deleted?

[bookman1502]

Here is the issue:

• A developer on our team deleted some choices in a choice list instead of setting them inactive as part of an update which included deleting, modifying, and creating choices in a choice list.
• We could not move the change to production because we did not want to cause issues with existing tickets which have the old choices that were deleted. We just don't want them to be an option anymore for new tickets.
• Backing out the update sets did not go successfully and there are still some missing choices in our dev and staging instances where the update sets were backed out. We do have a third instance called test, where we have not backed out the update sets and which sits between dev and staging in the release cycle (updates go form dev->test->staging).
• We can clone over dev and test easily from production but staging presents issues as it is used by multiple teams.
• We noticed in the update sets in test that there are no delete actions in any of the customer updates, only INSERT_OR_UPDATE changes to the choice list. Therefore, we were wondering if we cloned over dev and test, the developer sets the choices to inactive instead of deleting them, and then moves them to staging if it would recreate the old choices so as not to interfere with existing tickets which have them selected. This seems plausible because of the lack of DELETE actions in the update sets. We would greatly appreciate any thoughts and advice.

[Jon23]

Yes, that should create the missing choices.

Alternatively, instead of a clone, export the choice list as XML from your prod environment and import into DEV, TEST, STAGING and then mark as inactive in dev to capture in an update set and migrate through the instances.

[bookman1502]

Unfortunately we do not have admin access to the prod instance, so we'll have to go the first route instead. I'll mark your answer as correct once we successfully implement the solution.

[Sukraj Raikhraj]

Correct, if values associated with the sys_ids are in the instance , export as xml and import into each instances.