- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-18-2014 11:56 PM
Hi Guys,
I am not having much luck with uninstalling a custom application.
Background:
I created a custom application and published it to an update set. I than installed it on another instance by applying the update set.
To uninstall the application I attempted backing out the update set, however I got the error message Data Policy Exception: Name is mandatory.
The update set has been marked as backed out however the tables etc are still present in the test instance.
Questions:
Is this the right way to 'uninstall' an application?
I would have expected that backing out an update set would result in the system being returned to its previous state.
Experimented:
So being the curious person I am I tried deleting all the stuff which should have been deleted manually via the tables table etc however the update set now has issues when I try to apply it again. Something about duplicate tables. But I already deleted it.......
Any thoughts?
Thanks in advance,
Colin
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2014 05:49 PM
I would probably add:
- If you need to make changes, make a new update set to apply those changes.
- If you wish to re-publish an Application, you can, you just need to go to System Applications > Custom Applications, open your custom application on your development system, click "Publish to Update Set", then promote that update set to your Production Instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2014 05:40 PM
Thanks for the help guys, sounds like:
- When deploying an application if we want to get rid of it we can delete it
- We should only delete an application if we are really sure we never will use it as we will not be able to reapply the same update set to get it back
- Backing out update sets is a bad idea
Have I missed anything?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2014 05:49 PM
I would probably add:
- If you need to make changes, make a new update set to apply those changes.
- If you wish to re-publish an Application, you can, you just need to go to System Applications > Custom Applications, open your custom application on your development system, click "Publish to Update Set", then promote that update set to your Production Instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2014 05:59 PM
Oh good idea.
Oh and one more point:
- When applying the republished update set there will probably be errors complaining about clashes
Type
Remote update
Description
Available Actions
Error sys_security_acl_65c90ce15b70e580d16d799... Found a local update that is newer than this one Compare with local Show local record Show local update Accept remote update Skip remote update
- If you know that the changes will not be a problem ie all previous changes have been removed, than we can select all the false errors and choose the "accept remote update" option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2014 06:10 PM
Nice! Yep, you shouldn't have a problem.
Colin, if my assistance worked for you, I'd appreciate you marking one of my answers as correct. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-19-2014 06:12 PM
Thanks for the help!