Salesforce DX Developer Guide

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
Authorize Your Production Org
Create a Sandbox Definition File
Create, Clone, or Refresh a Sandbox
Track Changes Between Your Project and Org
Work with Data
Salesforce DX MCP Server and Tools
Development
Build and Release Your App
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
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.

Authorize Your Production Org

JWT and Web-based flows require a production org with sandbox licenses instead of a Dev Hub. However, it’s OK if your production org is also a Dev Hub org.

The examples in Authorize an Org Using the JWT-Based Flow and Authorize an Org Using the Web-Based Flow are geared toward scratch orgs. Follow these tips to successfully authorize your production org.

  • Be sure to use https://login.salesforce.com for sfdcLoginUrl in sfdx-project.json file. Alternatively, you can use org login jwt --instance-url to specify the URL directly on the command line. This value overrides the login URL you specified in the sfdx-project.json file.
  • Specify the username for your production org when running the org login jwt command. No need to specify a Dev Hub or indicate a default Dev Hub.
  • The JWT authorization flow requires that you create a connected app. When you create the connected app, log in to your production org, not a Dev Hub org.