Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Project Setup
Authorization
Scratch Orgs
Development
Build and Release Your App
Develop Second-Generation Packages (Beta)
Second-Generation Packaging
Types of Packaging Projects
Packaging for ISVs
Enterprise Customers
What’s a Package?
Before You Create Second-Generation Packages
Workflow for Second-Generation Packages
Plan Second-Generation Packages
Configure Packages in the sfdx-project.json File
Create a Package
Install a Package
Uninstall a Package
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

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

Enterprise Customers

If you’re an enterprise customer, you might be wondering: how can I use packaging in my Salesforce org? Isn’t packaging a partner-oriented feature? We have good news for you. Second-generation packaging enables technologies for developer-controlled packages. These packages let enterprise customers more easily develop and deploy their apps and functionality.

For most production orgs, metadata is contained in two buckets: a set of managed packages installed from the AppExchange or unpackaged metadata. At the same time, enterprises often invest in Salesforce customizations to support business processes and extend the power of the Salesforce platform.

Developer-controlled packages let you harness and extend your investments in the Salesforce platform in two ways. First, you can organize the unpackaged metadata in your production org into well-defined packages. You can then provide a continuous development and deployment framework for new apps, whether you have one production org or many.