function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
nick stonick sto 

Increasing Managed app limit beyond 1 manage app on or transferring code to new dev/partner org

Is there a way to increase the number of managed packages allowed (we already have 1 managed package and cannot upload another) or a simple way to transfer to a new dev org.  When we transfer via eclispe it strips out the first namespace 

aalbertaalbert

You can only have 1 Managed Package (ie 1 namespace) per Developer Edition org.

If you migrate the metadata of your managed package from one org to another, the namespace will be dropped since the destination org can not have the same namespace as the originating org. You can migrate all the components of your managed package into a new org and create a new, unique namespace.

 

Can you elaborate on what you are trying to do?
shillyershillyer

If you are looking to build another managed package that leverages the base code from your original managed package, you might want to consider using an extension package. More details here.

 

Hope that helps,

Sati
nick stonick sto

Thanks for the responses, our app is currently listed as managed-beta, do you know how to turn it back to unmanaged?
shillyershillyer

If you've never released a managed-released package and it's still only in managed-beta. You can delete the package and recreate it as unmanaged.

 

Hope that helps,

Sati