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
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
Differences and Considerations
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Partner Licensing Platform (Developer Preview)
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

Resolve Conflicts Between Your Local Project and Org

As a best practice, if conflicts exist for components in your local project or in the org, resolve them before moving forward. You can resolve the conflict manually, or overwrite one version of a component with another. Only overwrite changes if you're certain that the new version is the one you want to use.

Say you run force:source:status and see conflicting changes in your local project and in the org.

1=== Source Status
2STATE                     FULL NAME        TYPE           PROJECT PATH
3─────────────             ─────────        ─────────      ──────────────────────────────────────────────────────────────────
4Local  Add (Conflict)     WidgetClass      ApexClass      ./classes/WidgetClass.cls-meta.xml
5Local  Add (Conflict_     WidgetClass      ApexClass      ./classes/WidgetClass.cls
6Remote Changed (Conflict) Widget__c        CustomObject   ./objects/Widget__c/Widget__c.object-meta.xml

If you pull or push source, then the CLI reports these conflicts again and stops the operation from completing. To pull or push, resolve the conflicts, and then overwrite your local project or the org with the resolved file.

Overwrite Conflicting Changes

If you have no doubts that the local or remote version is correct, you can overwrite conflicting changes by including the -f | --forceoverwrite parameter when pulling or pushing changes.

To overwrite your local project changes with source from the org, include the -f | --forceoverwrite parameter when pulling changes.

1sfdx force:source:pull -u DevSandbox -f

After pulling source, your local project has the same version of WidgetClass and Widget__c that existed in the org. If you had different versions of these same files in your local project, they’re replaced with the versions that exist in your org.

To overwrite the org with source from your local project, include the -f | --forceoverwrite parameter when pushing changes.

1sfdx force:source:push -u DevSandbox -f

After pushing source, your org has the same version of WidgetClass and Widget__c that exists on your local project. If your org contained different version of those same components, they’re replaced with the versions from your local DX project.