Salesforce DX Developer Guide
Summer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Metadata Coverage
See Changes Identified by Source Tracking
Pull and Push Changes Identified by Source Tracking
Resolve Conflicts Between Your Local Project and Org
Get Change Information by Querying the SourceMember Object
Best Practices
Performance Considerations of Source Tracking
Retrieve and Pull Changes to Profiles with Source Tracking
Limitations for Salesforce DX
Newer Version Available
Differences and Considerations
As you get ready to work with source tracking, note these behavioral differences and
considerations.
-
Performance Considerations of Source Tracking
Source tracking performs extra functions to determine changes to source tracked components, such as running more queries. So, some commands can take a little longer to run when working with medium-to-large sized projects. If you’re working with small projects, you don’t notice any slowdown. -
Retrieve and Pull Changes to Profiles with Source Tracking
Retrieving and pulling profiles behaves a little differently with source tracking.