Timeline for Delete a managed release package
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 20, 2017 at 7:50 | comment | added | sfdcfox♦ | @Brian Yeah, the wording is a bit paranoid, but for an old hat it's just the same old news. Don't worry about it too much. Just make sure you deploy okay in the new org before you delete. | |
| Apr 20, 2017 at 7:06 | comment | added | Brian | I see. I have created a temporary org with a diff namespace for my managed package and am planning to upload it as a release package and then delete it. I have a different packaging org for the final managed package. The deletion shouldn't affect the main packaging org in anyway right? It is a different namespace altogether. Sorry being a little paranoid about this since some of these actions are irreversible and I don't want to get stuck going back n forth with the support! :) | |
| Apr 20, 2017 at 7:00 | comment | added | sfdcfox♦ | @Brian It's been a while, so I honestly don't remember, but I managed to get it done in my personal dev org, which has neither Partner Support or Premier Support. I think you're allowed so long as there's no installs of your package, but you'll want to experiment. Just go ahead and try. Worst case scenario is the system will tell you to contact support. Just make sure you're willing to commit to the deletion, because it is irreversible. | |
| Apr 20, 2017 at 6:54 | vote | accept | Brian | ||
| Apr 20, 2017 at 6:54 | comment | added | Brian | Thanks so much. Would the deletion of the package require a request to be raised with the salesforce support? | |
| Apr 19, 2017 at 19:18 | history | answered | sfdcfox♦ | CC BY-SA 3.0 |