If I select multiple files and right click>Deploy Source to org or Retrieve source from org, it only deploys the file that I right clicked on and not all files that were selected.
The command output shows only one file that it is trying to source:deploy, so I think it is possibly an extension issue.
Both files are deployed/retrieved
Only the file that is right clicked on is retrieved
It seems like there is a multiple file command for at least the deploy part (sfdx.force.source.deploy.multiple.source.paths) but it isn't mapped to a right click action
VS Code Version: 1.32.3
SFDX CLI Version: 7.1.4-79f97a7df8
OS and version: Windows 10 1803
Related to #862
@ntotten Is there any update on that? I looked in #862 and it doesn't seem to be resolving this issue, which is critical in situations of multiple dependencies between components.
I would like to add my voice to those requesting this feature. It's very confusing from a usability perspective that only the right-clicked file is deployed.
Hi @jflowers45 - Thanks for weighing in. The way we're thinking about solving this is to provide a way to select multiple metadata types or files and generate a manifest from the Org Browser. This would then allow you to retrieve or deploy with that assortment of items at any time - no need to carefully right-click on them all each time. (This is a similar concept to the 'working set' that Nate described in #862). This is a roadmap item and I'd welcome any other feedback on the tentatively-planned approach.
@smaddox-sf that would be awesome! It would be more awesome if this is taken care at the CLI via a command where one can pass in all the metadata elements and metadata type.
This way this functionality won鈥檛 be tied to this extension pack and org browser only!
Salesforce CLI retrieve command by metadata is great but gets verbose and repetitive as soon as we have more number of components and metadata types.
This is a must feature. With Eclipse IDE and Force.com plugin, we were able to achieve this.
As a workaround, I am adding the components to a new project and deploying the whole project. This might not work for all.
Most helpful comment
@ntotten Is there any update on that? I looked in #862 and it doesn't seem to be resolving this issue, which is critical in situations of multiple dependencies between components.