Deleting and recreating a field with the SAME name on [task] (or a child table) adds 'sys_metadata_delete' records to the Update Set that captures the recreation of the field. - Known Error

Deleting and recreating a field with the SAME name on [task] (or a child table) adds 'sys_metadata_delete' records to the Update Set that captures the recreation of the field. Description Deleting and recreating a field with the SAME name on [task] (or a child table) adds 'sys_metadata_delete' records to the Update Set that captures the recreation of the field.

These 'sys_metadata_delete' records interfere with the field creation on the target instance. At commit time, the "Confirm Data Loss" warning is displayed: "If you commit this update set, the system will automatically delete all data stored in the tables and columns that are defined in these Customer Updates:"

As a result, the field has a [sys_dictionary] record, a [sys_documentation] record but no [sys_storage_alias] record. The label appears blank and cannot be changed.

Steps to Reproduce

Steps:

Create a new Update Set and make it current. From [sys_dictionary], create a new field on a table extending [task]. (For example: [incident], new data/time field). Make a note of the name. Complete and export the Update Set. Create another Update Set and make it current. Delete the field created at step 2. Complete and export the Update Set. Create another Update Set and make it current. From [sys_dictionary], create a new field with the SAME name as step 2 >>> Column label and name should be the same. Access the Update Set and observe that it includes 2 'sys_metadata_delete' records > 1 for the Dictionary and 1 for the Documentation. Complete and export the Update Set. On another instance, apply all 3 Update Sets in order.

> Current behavior: The field has a [sys_dictionary] record, a [sys_documentation] record but no [sys_storage_alias] record.

> Expected behavior: The 'sys_metadata_delete' records should not be included in the Update Set when recreating the field.

Workaround This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.

As a workaround, remove the extra 'sys_metadata_delete' records from the Update Set that recreates the field.