Second-Generation Managed Packaging Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Second-Generation Managed Packages
What’s a Second-Generation Managed Package?
Set Up Your Development Environment
Before You Create Second-Generation Managed Packages
Scratch Orgs and Package Development
Workflow for Second-Generation Managed Packages
Components Available in Second-Generation 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
Get Started with the License Management App
Lead and License Records in the License Management App
Modify a License Record
Refresh Licenses for a Managed Package
Extending the License Management App
Package and Package Version Object Fields
License Object Fields
Adding Custom Automation to License Management App Objects
Move the License Management App to Another Salesforce Org
Troubleshoot the License Management App
Best Practices for the License Management App
Troubleshoot Subscriber Issues
Manage Features in Second-Generation Managed Packages
Get Started with AppExchange App Analytics
Gaps Between First-Generation and Second-Generation Managed Packaging
PDF

Package and Package Version Object Fields

The License Management App (LMA) includes a Package custom object and a Package Version custom object. These objects display details about each 1GP or 2GP package and package version you’ve listed on AppExchange.

To view details about a package record, from the LMA, select the Packages tab, and then select the package name. You can view package versions in the Package Version related list.

The LMA creates the package records, which contain critical information for tracking your licenses and packages. Treat these fields as read-only and ensure that your object permissions protect package records.

Note

Package Custom Object Fields Description
Developer Name The name of the org that owns the package. For 1GP, the org name is the packaging org. For 2GP, it’s the Dev Hub org.
Developer Org ID The 18-character ID of the org that owns the package. For 1GP, the org ID is the packaging org ID. For 2GP, it’s the Dev Hub org ID.
Last License Refresh The date when the License Refresh tool was last run.
Latest Version The most recent package version you’ve released.
Lead Manager The owner of the lead records that the LMA creates when a customer installs your package.
Next Available Refresh The date when the License Refresh tool can be run again.
Owner The LMA owns all package records.
Package ID The 18-character ID that identifies the package. This ID starts with 033.
Package Name The name you specified when you created the package.
Package Version Object Fields Description
Package The package name and links to the package record’s detail page.
Package Version Name The name you specified when you created the package version.
Release Date The date you created this package version.
Version Number The version number in major.minor.patch format. For example, 3.1.0.
Version ID The 18-character ID of this package version.