2

We have a Managed package, and we want to create another Managed Package extension in the same Dev org. Can I create 2 Managed Packages in 1 Dev org? If not, what are my options and do I have to pay Salesforce to increase the limit?

12

You cannot create two managed packages in one dev org, you can only have one namespace created per DE org.

Your options are to create another DE org and install the first managed package in there. Then, once you start to reference the first managed package in the new DE org, then that package becomes an extension of the first. Once you release your second managed package, subscribers would have to install the first package and then the second.

  • Thanks Phil. Are you sure about this? So you are saying there is no way I can have another Managed Package even if I`m ready to pay for another add on package? Just want to make sure I understand this correctly. – Wendy Jun 14 at 10:42
  • 2
    Yes, you can only create one managed package per developer org. – Phil Hawthorn Jun 14 at 10:52
  • You can only develop one managed package in one DE org, there is a 1:1 relationship between the Packaging org (i.e. the DE org that is used to release the package from) and the Package. I work for an ISV and I'm sure if there was a way, paid or otherwise, we'd know about it by now. – Phil Hawthorn Jun 14 at 11:02
  • 3
    I should add, I'm referring to 1st generation managed packages, there may be other options with 2nd gen managed packages but is currently in beta i believe. – Phil Hawthorn Jun 14 at 11:10
  • Understood. Thank you very much Phil. – Wendy Jun 14 at 11:33
7

Phil is correct for 1st gen packages.

2nd gen packages are indeed not out of beta yet. Notably, Salesforce hasn't fully documented exactly how 2GP will get connected to Publishing Console, Security Review, LMA, COA etc. But going by current info, here's basically how it would work once they go live:

  • Your DE org will still "own" the namespace.
  • You'd create a link from your Production org, which has a Dev Hub, to the DE org so that it "registers" the namespace and has permission to use it in 2GP.
  • Your Dev Hub can now create scratch orgs with this namespace (this part is already GA).
  • Your Dev Hub can now create packages with this namespace, and they can be multiple different packages. (beta)
  • Different packages with the same namespace have some special rules on what they can/can't share with each other. (beta)
  • The "multiple packages" bit is for internal organization of your managed package. You can still only have one managed package per developer org. I don't think they've stated that this will be changing any time soon. – sfdcfox Jun 14 at 14:48
  • My understanding is that under 2GP it will be possible to release multiple independent or dependent packages with the same namespace, using DX. The packaging org will no longer be the source of truth for packaging. – Charles T Jun 15 at 13:36
  • Oh, that would be a nice addition. Handling so many different logins for all those dev orgs was a royal pain. We'll have to see how it works once it comes out of beta. – sfdcfox Jun 15 at 15:44
  • 1
    See this for example: releasenotes.docs.salesforce.com/en-us/summer18/release-notes/… A new access modifier that determines whether different packages in the same namespace can access the same Apex class. – Charles T Jun 16 at 15:01
  • 2GP is coming out of beta in the Winter '20 release. See the release documentation here – Brian Miller Sep 25 at 12:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.