[SalesForce] Ability to enable Dev Hub / Unlocked Packages for Partner Developer Edition Org

I'm using a Partner Developer Edition org to develop features for a managed package (which resides in a different org).

According to the Winter '19 Release Notes, Developer orgs should have the Dev Hub option available if they're not using a namespace.

My Partner Developer Edition org doesn't have a namespace, but I can't see the Dev Hub option in Setup, which is preventing me from using Unlocked Packages to push new functionality to other orgs.

Question: Am I missing anything, or maybe Partner Developer Edition orgs by definition don't have the Dev Hub option?

Best Answer

From the Enable Dev Hub in Your Org article, it implies that you can only enable Dev Hub in the Partner Business org:

Partner trial orgs signed up from the partner community have different scratch org limits. See Scratch Org Allocations for Partners. Partners can create partner edition scratch orgs: Partner Developer, Partner Enterprise, Partner Group, and Partner Professional. This feature is available only if creating scratch orgs from a Dev Hub in a partner business org. See Supported Scratch Org Editions for Partners in the ISVforce Guide for details.

(You can only create scratch orgs against a Dev Hub enabled org, and same with unlocked packages)

Related Solutions

[SalesForce] Do I need to enable Dev Hub in the PROD Org

Dev Hub can be enabled in Developer Edition orgs, but the scratch org limits are significantly lower than in paid Salesforce production orgs. In a Developer Edition org, the limits are just 3 active and 6 daily scratch orgs, which might suffice for an individual developer who is not using continuous integration but can be stifling in a process that likes to use a lot of orgs. It's not feasible to share a Developer Edition Dev Hub across a team; each developer would need their own.

Production orgs, as described in the linked documentation, offer an order of magnitude more scratch orgs. To use Dev Hub in production, you can request special free, limited access licenses (I wasn't sure if that's what you were alluding to in your question) to enable developers to authenticate and create scratch orgs against Prod, without viewing CRM data.

Of course, some organizations may be unwilling for compliance or process reasons even to use those licenses, in which case you don't have much recourse other than a separate paid org or multiple Developer Editions.

[SalesForce] Scratch org: how to retrieve metadata

A scratch org is a completely blank Salesforce org that's divorced from any data/metadata in any other org in your Salesforce universe (including the Dev Hub - your Dev Hub org just gives you the ability to create scratch orgs and managed them via the UI). So there's no metadata to retrieve from the scratch org itself.

If you want to pull metadata from a different org, like the Dev Hub org or a Production / Sandbox org, into your scratch org, do the following:

First authorize the org you'd like to retrieve metadata from:

sfdx force:auth:web:login -a MyDevOrg

Use force:source:retrieve to pull relevant metadata you're looking for from that org. See the documentation on all the options of how to pull specific metadata. A sample of how to pull all classes and triggers will look something like this:

sfdx force:source:retrieve -m ApexTrigger,ApexClass -u MyDevOrg

Push that metadata you just retrieved from your local project into your scratch org

sfdx force:source:push

Best Answer

Related Solutions

[SalesForce] Do I need to enable Dev Hub in the PROD Org

[SalesForce] Scratch org: how to retrieve metadata

Related Topic