New answers tagged

0

For any superbadge, you will have to install a package before starting. Copy the name of the package and use this command in the terminal. $ sfdx force:source:retrieve -n NameOfThePackage This will retrieve all the components in the package into a new folder named as the package. Hope this helps.


1

You cannot activate/deactivate flows using Metadata API. Check limitation details here. However, previously flows were always deployed as inactive and now you can deploy a new active version of flow via Metadata API/Change sets and please note this setting doesn't appear in non-production orgs (such as scratch, sandbox, and developer orgs). Check more ...


0

You would need to deploy the Flow metadata changing the status attribute. Using sfdx force:source:deploy for example


0

Had the same issue, it is when use the extension on the command palette. Go to the terminal and run: sfdx force:source:retrieve -x manifest/package.xml


0

For my case the above where not working, because I found that I had multiple sfdx folder due to installation from installer + npm : I had one installed in the following path : C:\Users<>\AppData\Local\sfdx and another one here : C:\Program Files\sfdx The one installed via npm was at some point in time doing conflict with the other installation. I ...


1

In my Case the issue was that i had an EMPTY JSON-File in the User Home SFDX Directory. On Windows Machines: C:\Users\[YOUR USERNAME]\.sfdx There is also a Log-File "sfdx.log" which also gives detailled insight into the issue. In my Case there was a code line like this: {"name":"sfdx","hostname":"ANONYM-PC",&...


3

Use sfdx force:source:push rather than ...:deploy Use sfdx force:source:pull rather than ...:retrieve Then you can use sfdx force:source:status to see changes. If you are using a Scratch Org, you should just be able to use the above commands. If you are using a Sandbox, in your Dev Hub org you will need to go to Setup >> Dev Hub and check Enable ...


3

You can use diff against the org commands for a UI that shows changes from your org (in both directions!). You can also see your current status from a terminal command: sfdx force:source:status Or you can deploy any changes that are detected in your workspace: sfdx force:source:push You can also go in to your Settings (File > Preferences > Settings &...


0

sfdx force:source:retrieve -m "WorkflowFieldUpdate:ObjectName.FieldupdateName" example: sfdx force:source:retrieve -m "WorkflowFieldUpdate:SBQQ__Quote__c.Update_Approval_Status_to_Approved" for alert replace "WorkflowAlert"


0

This issue was occuring due to Salesfoce CLI update. It has been resolved with the latest release 7.115.0 Refer here for details on the issue and resolution


Top 50 recent answers are included