Back out an update set
-
- UpdatedAug 3, 2023
- 3 minutes to read
- Vancouver
- Building applications
The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
You can back out changes to existing records for any committed update set.
Before you begin
Role required: admin
About this task
Backing out an update set creates delete updates in the current update set. If you commit, back out, and then reapply a remote update set, errors appear in the previewer because the deleted updates are considered more recent changes and cause collisions.
Warning: Do not back out the Default update set.
This action can damage the configuration of the instance.
The back out process reverses both record-level updates and changes to the
dictionary. Some changes caused by a back-out can result in data loss. These are the
expected results of the back-out process:
Warning: Backing out an update set that belongs to
an update set batch may affect other update sets in the batch. For more
information, see Back out batched update set.
- If the sys_package is global, it is deleted.
- If the sys_package is not global, and it has a value, a warning displays that there is no deletion. Rather, the sys_update_xml is put into the default update set and the record is left in place.
Procedure