New [sys_choice] records should show as an INSERT OR UPDATE in the Update Sets but instead are incorrectly being logged as a DELETE Action.Issue Whenever a new [sys_choice] record is created for a table and element , or an existing Choice is edited, it is saved as a DELETE Action in an Update Set instead of an INSERT OR UPDATE. Steps to Reproduce Login to an instance as 'admin'2. Navigate to: System Update Sets > Local Update Sets and create a new Update Set. Click on 'Submit and Make Current'.3. Navigate to: System Definition > Dictionary.4. Search for any table and open any record with Type as 'Collection'. Dictionary Entry page will be loaded.5. There is related list 'Choices' associated to this dictionary.6. Click on New and create a new Choice.7. Set the Element field to an invalid/non-existent field under the table selected then click Submit.8. Navigate to the [sys_update_xml] table and find the corresponding update. Verify it has an Action of DELETE. This causes an issue when the Update Set is promoted to another instance because the actual changes have not been recorded. Worse, it deletes all the Choices for the target Table and Element, ReleaseAll releasesCauseThe root cause of this issue is that there is not a related record for the table and element in the [sys_choice_set] table. This is why it cannot find the Choice Set when updating the Choice and instead interprets the update as a DELETE entry. In the screenshot provided below, the field 'u_closure_source"' has no association with any table. Hence any Choices will be logged as DELETE Action in the [sys_update_xml] table. ResolutionNavigate to [sys_choice_set] and manually create a new Choice Set on table "xxxxxx" and element "xxxxxx". This should generate a relationship between the table and element and the existing Choices. Related LinksKB0656146 provides an overview of Choices in ServiceNow.