Second-Generation Managed Packaging Developer Guide

Second-Generation Managed Packages
What’s a Second-Generation Managed Package?
Set Up Your Development Environment
Before You Create Second-Generation Managed Packages
Know Your Orgs for Second-Generation Managed Packages
Link a Namespace to a Dev Hub Org
Namespaces for Second-Generation Managed Packages
Create and Register Your Namespace for Second-Generation Managed Packages
Key Concepts in Second-Generation Managed Packaging
How Manageability Rules and Ancestry Impact Upgrades for Second-Generation Managed Packages
Which Package Dependencies Work with Second-Generation Managed Packages?
Scratch Orgs and Package Development
Workflow for Second-Generation Managed Packages
Components Available in Managed Packages
Behavior of Specific Metadata in Second-Generation Managed Packages
Develop Second-Generation Managed Packages
Install and Uninstall Second-Generation Managed Packages
Prepare to Distribute Your Second-Generation Managed Package
Push a Package Upgrade for Second-Generation Managed Packages
Advanced Features for Second-Generation Managed Packages
Best Practices for Second-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in Second-Generation Managed Packages
Get Started with AppExchange App Analytics
Gaps Between First-Generation and Second-Generation Managed Packaging
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Which Package Dependencies Work with Second-Generation Managed Packages?

With second-generation managed packages (managed 2GP) you can easily develop small interdependent packages and share logic between them. If you design your app to rely on small modular packages, both package creation and package installation are faster, and you’re less likely to hit limits.

To develop small, modular packages, you create dependencies between your packages. A package dependency is when metadata contained in one package depends on metadata contained in another package. These dependencies allow you to extend the functionality of the base package with components and metadata located in a separate package.

When working with both first-generation (managed 1GP) and second-generation (managed 2GP) packages, only certain combinations of packages are supported.

Can a managed 2GP package depend on a managed 1GP package? Yes
Can a managed 2GP package depend on another managed 2GP package? Yes
Can a managed 1GP package depend on a managed 2GP package? No. This dependency isn’t supported, and we block the installation of managed 2GP packages in managed 1GP packaging orgs.

We can override this behavior on an individual basis. To share your scenario and request an override, log a case with Salesforce Partner Support.

We’re investigating how to support this dependency scenario more broadly.
Can a managed 1GP package depend on another managed 1GP package? Yes
Can a managed 2GP package depend on an unlocked package? Not recommended. However, you can build an unlocked package that depends on a managed 1GP or managed 2GP package.