For a completed update set that is not a retrieved update set, back out does not consistently get the instance back to where it was before applying the update set (it may just remove the update set but not revert the applied changes). This is the case for both local update sets (backing out changes which were made locally) and also for pulled/pushed update sets in team development.

Given the inconsistencies, it would be better to disable the button when not expected to work.

Steps to Reproduce


1. Create an Update Set and make it the default.
2. Create an app and a table.
3. Set the update set to Complete.
4. Back out the update set.  

Result: The update set appears.

Using team development to push the changes to the parent is another, perhaps more common, scenario where a local update set is completed and cannot always be fully backed out.


If you are able to upgrade, review the Fixed In field to determine the versions that have a permanent fix to this issue.

You can also subscribe to this known error article (click the Subscribe button at the top of the article) to receive notifications when more information is available about this issue.

Related Problem: PRB598943

Seen In

Calgary Patch 2 Hot Fix 5
Dublin Patch 3
Eureka Patch 1 Hot Fix 2
Eureka Patch 6

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2015-10-05 13:01:18