[SalesForce] VSCode SFDX: Retrieve Source from Org failing

I have Lightning Web Components called myList, and when I try to do SFDX: Retrieve Source from Org, to get my classes from Apex class, I get the following error:

20:32:09.428 Starting SFDX: Retrieve Source from Org === Retrieve Warnings FULL NAME TYPE
MESSAGE
───────── ────────────────────────
──────────────────────────────────────────────────────────────────────
myList
LightningComponentBundle Entity of type 'LightningComponentBundle' named 'myList' cannot be found
20:32:10.344 ended SFDX: Retrieve Source from Org

And something else. If I'm trying to do SFDX: Retrieve Source from Org and I have no Lightning Web Components in the lwc folder, I get the following error:

19: 21: 30.12 Starting SFDX: Retrieve Source from Org
No components in the package to retrieve

I do not understand the connection between Retrieve Source from Org and Lightning Web Components in the project. I would love an explanation!

Best Answer

I created a new project with the command: SFDX: Create Project with Manifest.

Then right-click on the package.xml file in the manifest folder, and select SFDX: Retrieve Source in Manefist from Org.

It worked.

Related Solutions

[SalesForce] How to retrieve Lightning Web Components using Ant Migration tool or mdapi:retrieve command from SFDX

The new Metadata API component is called LightningComponentBundle

The following XML code should be added to package.xml:

<types>
    <members>*</members>
    <name>LightningComponentBundle</name>
</types>

[SalesForce] Unable to Retrieve Source from Sandbox

The activation event for Salesforce's official extension is it looks for the file sfdx-project.json file in the workspace. Hence make sure you have the sfdx-project.json in the project workspace root folder.

Also, make sure you have .sfdx folder and also have an sfdx-config.json file with defaultusername set.

Also, try to reload the project using the reload command in command Palette. If the issue still persists feel free to post what your project structure looks like.

NOTE: The official extension has got better since I wrote the answer. It now has all the features that were missing and was supplemented by my extension.

Also yes I created another extension because the official extension has few issues that they are trying to figure still

1.Performance issues for saving single files. You can easily compare that what I have today is at least 2X faster than what you get from the official extension.

This is because they use Metadata API even for single file deploy which as per salesforce has performance issues and they plan to fix it in an upcoming release.

2.The package.xml generation is easier using changesets or unmanaged package container and the official extension does not offer a good GUI to generate them.

3.Official extension uses apex lang server for auto-completion that almost consumes a lot of my CPU. I would rather not have autocompleted than an extension trying to consume my whole CPU.

4.Official salesforce extension does not manage conflict with the server for Nonscratch orgs like sandboxes. It's in their roadmap.

5.Salesforce recommends using the new source format which I too recommend however if you are finding issues with that format the extension I have supports both DX typed source format and traditional source format.

Overall the idea of me building an extension was not to replace Salesforce's official extension instead supplement it with some missing capabilities till salesforce figures all of them.

Related Topic