Salesforce DX Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
How Salesforce Developer Experience (DX) Tooling Changes the Way You Work
Provide Developers Access to Salesforce DX Tools
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Work with Data
Development
Build and Release Your App
Unlocked Packages
What’s an Unlocked Package?
Package-Based Development Model
Before You Create Unlocked Packages
Know Your Orgs
Create Org-Dependent Unlocked Packages
Workflow for Unlocked Packages
Configure Unlocked Packages
How We Handle Profile Settings in Unlocked Packages
Develop Unlocked Packages
Create and Update an Unlocked Package
Create New Versions of an Unlocked Package
Simplify Unlocked Package Development by Creating and Specifying an Org Shape
Use Branches in Unlocked Packaging
Target a Specific Release for Your Unlocked Packages During Salesforce Release Transitions
Guidance for Package Version Numbering
Code Coverage for Unlocked Packages
Considerations for Promoting Packages with Dependencies
Release an Unlocked Package
Update an Unlocked Package Version
Hard-Deleted Components in Unlocked Packages
Delete an Unlocked Package or Package Version
View Package Details
Push a Package Upgrade for Unlocked Packages
Install an Unlocked Package
Migrate Deprecated Metadata from Unlocked Packages
Uninstall an Unlocked Package
Transfer an Unlocked Package to a Different Dev Hub
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Simplify Unlocked Package Development by Creating and Specifying an Org Shape

If your package’s metadata depends on a complex set of features, settings, or licenses, it can be difficult to declaratively specify these dependencies in a scratch org definition file. Instead, create an org shape of your production org, or another development org, and specify that source org’s ID in your scratch org definition file. During package creation, we mimic the source org’s environment when we build and validate your package’s metadata.

Before using this feature, get familiar with how Org Shape for Scratch Orgs works.

Then enable the scratch org setting in your source org, generate the org shape, and edit your scratch org definition file to include the org name and 15-character source org ID.

{
  "orgName": "Acme",
  "sourceOrg": "00DB1230400Ifx5"
}