Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
What’s a Package?
Comparison of 2GP and 1GP Managed Packages
Namespaces
Package IDs and Aliases
Before You Create Second-Generation Managed Packages
Workflow for Second-Generation Packages
Configure Packages
Best Practices for Second-Generation Managed Packages
Frequently Used Packaging Operations
Create a Package
Push a Package Upgrade
Install a Package
Uninstall a Package
Publishing Your App on AppExchange
Gaps Between First-Generation and Second-Generation Managed Packaging
Test and Respond to the New Order Save Behavior
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

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

Publishing Your App on AppExchange

If you’ve published a 1GP managed package, you’ll notice the process for publishing a 2GP managed package is different. Once you link your Dev Hub org to the AppExchange publishing console, all your released 2GP package versions are visible in the publishing console.

To list an app on AppExchange, it must pass the AppExchange security review. For more information, see Pass the AppExchange Security Review.

Link Dev Hub to the AppExchange Publishing Console
  • Log in to the Salesforce Partner Community.
  • Select the Publishing tab, and then select Organizations.
  • Click Connect Org, and enter the login credentials for your Dev Hub org.
Register Your Package
  • From Packages tab, locate the package version you want to register, and click Register Package in the Licenses column. Registering a package links the package to your license management app.
  • Enter the login credentials for the Dev Hub org associated with the package, in the modal window.
  • Set the default license behavior for the package, including trial length, and number of seats included with the license, and click Save.

Packages that share a namespace can be associated the same License Management Org (LMO), or you can associate the packages with different LMOs.