1

I must say that the documentation and information for Packaging is quite confusing.

That being said, I'm trying to become as well versed in Packaging so I'll be ready for a release in the near future.

Here is the issue, in screen one, I have permission to create Managed and Unmanaged Packaged

Screen 1

In Screen 2, which follows, there are only options for Managed Beta and Release. I believe this is a DE environment.

Screen 2

Thank you.

2
  • The images are reversed. Sorry about that.
    – Quade
    Commented Dec 6, 2013 at 18:34
  • No problem, I've fixed the order for you now. Commented Dec 6, 2013 at 18:55

2 Answers 2

2

Once you have defined a namespace (as in 'trmn' in your case) in a DE org, you can only have one managed package defined in it, though you can have further unmanaged packages if you wish. A package can only be of one type, managed or unmanaged, not both at once. The docs do not really state why you would want to have multiple packages in a DE org (mutiple unmanaged or one managed and multiple unmanaged), but you can.

What your seeing in your second screenshot is the options shown when you attempt to 'upload' your managed package (the one associated with the 'trmn' namespace). Hence you only see references to the term 'Managed'. If you create another package (which will have to be an unmanaged one), and attempt to upload this you will see a screen like this when clicking the Upload button.

enter image description here

The ISV Force guide is a great reference to managed packages and the process,

4
  • Thank you that makes sense. The part I was missing is that you cannot create more than one Managed Package in one org.
    – Quade
    Commented Dec 6, 2013 at 19:10
  • Your most welcome! :-) Commented Dec 6, 2013 at 19:11
  • hi @AndrewFawcett, what would be a valid scenario for having both an unmanaged and managed package in the same org?
    – BarCotter
    Commented Dec 6, 2013 at 19:20
  • From my perspective, as an ISV, we don't develop in the packaging org, its really just used as a means to release. So I'm struggling to think of why you would. I have in the past in some adhoc cases, just created one to get some components copied out of the org and into another, then deleted the unmanaged package afterwards. That can be useful. Commented Dec 7, 2013 at 20:25
0

You can create more than one package in your org, but only one can be managed. The managed package can never be uploaded as "unmanaged", but you can create a new package and upload that one as unmanaged.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .