First-Generation Managed Packaging Developer Guide

First-Generation Managed Packages
Why Switch to Second-Generation Managed Packaging?
Move to 2GP: Migrate Your Managed Packages with Ease
Register a Namespace for a First-Generation Managed Package
Create a First-Generation Managed Package Using a UI
What Are Beta Versions of Managed Packages?
Create a Beta Package for First-Generation Managed Packages
Create and Upload a First-Generation Managed Package
Publish Extensions to Managed Packages
View Package Details in First-Generation Managed Packages
Notifications for Package Errors
Create a First-Generation Managed Package using Salesforce DX
Components Available in First-Generation Managed Packages
Behavior of Specific Metadata in First-Generation Managed Packages
Package and Test Your First-Generation Managed Package
Update Your First-Generation Managed Package
Publish Upgrades to First-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in First-Generation Managed Packages
AgentExchange App Analytics for First-Generation Managed Packages
Developing and Distributing Unmanaged Packages
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Publish Extensions to Managed Packages

An extension is any package, component, or set of components that adds to the functionality of a managed package. An extension requires that the base managed package is installed in the org. For example, if you have built a recruiting app, an extension to this app can include a component for performing background checks on candidates.
Available in: Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

User Permissions Needed
To create packages: Create AppExchange Packages
To upload packages: Upload AppExchange Packages

Building a new app? Have you considered using second-generation managed packages? Flexible versioning and the ability to share a namespace across packages are just two reasons why developers love creating second-generation managed packages. We think you’d love it, too. To learn more, see: Why Switch to Second-Generation Managed Packages, and Comparison of First- and Second-Generation Managed Packages.

Note

The community of developers, users, and visionaries building and publishing apps on AgentExchange is part of what makes Salesforce Platform such a rich development platform. Use this community to build extensions to other apps and encourage them to build extensions to your apps.

When working with both first-generation (1GP) and second-generation (2GP) managed packages, only certain combinations of packages are supported. See: Which Package Types Can Your Package Depend On?

To publish extensions to a managed package:

  1. Install the base package in the Salesforce org that you plan to use to upload the extension.
  2. Build your extension components.

    To build an extension, install the base package and include a dependency to that base package in your package. The extension attribute automatically becomes active.

    Note

  3. Create a package and add your extension components. Salesforce automatically includes some related components.
  4. Upload the new package that contains the extension components.
  5. Proceed with the publishing process as usual. For information on creating a test drive or registering and publishing your app, go to Salesforce Partner Community.

Packages can’t be upgraded to Managed - Beta if they’re used within the same org as an extension.

Note