- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2017 06:41 AM
Hello,
If we wanted to go back to the baseline change application, how would we go about this? For example, we don't want to keep our customizations, and we want to revert the change application ONLY, is there a way to do this without having to revert each customization manually based on the last upgrade?
Thank you in advance!
Laurie
Solved! Go to Solution.
- Labels:
-
Best Practices
-
Instance Configuration

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2017 06:15 AM
In general, we recommend that after every update (at least when you upgrade to a new release) you go through the skipped upgrades and check them (at least the higher priority ones), and make a conscious decision about them (revert, merge, keep).
If you do revert, you will not revert to the status it was before you did the modification, but to the latest status of the product (which might be quite different, if your modifications were made on an earlier release). So you need to perform a lot of tests to make sure you did not miss anything and all artefacts are from the same (current) release, or things might not work as expected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2017 06:17 PM
Hi Laurie,
I'm not aware of something like that.
Perhaps the best will be to go to the change list and select Configure >> All. This will bring the complete list of some of the most important objects related to the Change module. Sort the list based on when these where last updated and smartly (with good judgment) start going back to the latest OOB version from your latest upgrade (through the version related list). Take note of what functionality you're loosing so that you also update other system objects that may require changes (for instance: script includes, etc...).
I understand this is a manual process, but hopefully something that will allow you to review a smaller amount of elements.
I hope it helps!
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2017 06:11 AM
Thanks, Berny! I will do that along with Julian's suggestion.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2017 03:56 AM
This is going to be tricky, so you better test this well on a sub-production instance.
You can revert all your changes by going to your Upgrade Monitory and go to the "skipped" changes, and revert all changes that are related to the change process. To get that list, you can also check out your update table (sys_update_xml).
But if you changed the data model, that means you might lose data if you revert changes, so you have to test this carefully before you actually revert anything.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2017 06:10 AM
That is what I was thinking, too. Thank you for confirming. This will be interesting. It may be a while before we attempt this, but when we do, I will post the results!
Cheers from Kansas!
Laurie