SFDX: sfdx force:src:pull does not detect Action Override added to a CustomObject or Custom Lightning App
Last updated 2019-09-07 ·Reference W-3750342 ·Reported By 4 users
When you add an Action Override to a Custom Object or Custom Lightning App that already exists in your local copy of the metadata, the sfdx force:src:pull does not detect the change. The updates to the Custom Object or Custom Lightning App are not pulled to your local.
1. Spin up a scratch org
2. Push a workspace that contains MyCustomObject
3. Add a new VF Page
<h1>New Override Page</h1>
4. Set this page as the Action Override for the "New" action of MyCustomObject__c
5. Invoke sfdx force:source:pull
1. Create scratch org (with project)
2. Create a custom app
3. Create a custom object
4. sfdx force:source:pull to pull the current metadata to your local
5. In Lightning App Builder, create a custom record page for the custom object.
6. Activate the page as the "App Default" for the custom app you created.
7. sfdx force:source:pull
sfdx force:source:pull detects the new Action Override and pulls down the custom Object or Custom App metadata with this update.
sfdx force:source:pull does not detect the change to the custom object or app, it only pulls down the new page
1. Manually add the needed actionOverride to the object or application metadata. For example, you could pull the application metadata through Metadata API and copy it over.
2. Use force:source:retrieve to pull the whole package of metadata instead.
3. Make another kind of change to the custom object or app that will be detected. The correct metadata with the action override included will also be pulled with this new detected change.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.