New answers tagged

0

If it is showing that CLI is not installed, then the possible is you haven't set the path or set the wrong path. To set PATH: Press Start Button Type Environment Go to System Environment setting Go to Advanced Environment Variables - there are two options: user variable for admin and system variables Go to system variables Double click on Path Add new row ...


3

I added the same comment to Saleforce github issues for VS Code Salesforce dx plugin, and it was marked as a bug by SF team. Seems the issue is with Aura Component extension for VS Code by Salesforce. It can be checked at below link https://github.com/forcedotcom/salesforcedx-vscode/issues/1592


2

There is a SFDX Command to open the current org that VS Code is working against: > SFDX: Open Default Org Additionally, on the bottom left of the status bar the currently connected org alias is shown and clicking the icon besides it opens the org. Under the hood both the "Open Default Org" and status strip button do the same thing. They issue the SFDX ...


2

My Question is can you just debug your Classes and Triggers or do you have to have a Test Class First? You will need to have a Test Class and execute it before you can debug your underlying Apex classes using Apex Replay Debugger. The way it works is that once you run a Test Class, logs are generated. And then you use those logs to debug your classes. So ...


3

You can execute the query written on the Apex class by following the below step: https://trailhead.salesforce.com/en/content/learn/projects/quickstart-vscode-salesforce/use-vscode-for-salesforce


0

Make sure the component doesn't already exist.i.e. if you are deploying helloWorld and if there is already an aura component with same name, you will get this error. This can be checked in deployment status.


0

One of the reasons may be conflict in your aliases files. You can find following folder on your computer: %USERPROFILE%/.sfdx and find there file alias.json. There would be all your used aliases and you can investigate if you have any conflicts.


0

Error : { Error: spawn cmd ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19) at onErrorNT (internal/child_process.js:415:16) at process._tickCallback (internal/process/next_tick.js:63:19) errno: 'ENOENT', code: 'ENOENT', syscall: 'spawn cmd', path: 'cmd', spawnargs: [ '/c', 'start', '""', '/b', 'login.salesforce....


0

I encountered this issue as well, but was able to resolve the issue via the instructions in the Salesforce DX Developer Guide: Unable to Work After Failed Org Authorization Link content posted here for convenience & in case of link corruption: Sometimes you try to authorize a Dev Hub org or a scratch org using the Salesforce CLI or an IDE, but you ...


2

You can try this too $ sfdx force:source:retrieve -m LightningComponentBundle


0

If you have correctly installed VS Code, SFDX CLI and the SF VS Code Extensions then you might just want to try restarting your machine. I have had this same issue occur to me twice on 2 different machines and each time I have only restarted my machine and the issue goes away. I hope this works for you!


3

It might be the case that you need to add a reference to the specific package in your package.xml, alongside the wildcard (*) that's collecting the LWCs that you can see. For help amending the package.xml, I'd refer to the Packages section of this official samples doc. I'm guessing it'd look like this: <types> <members>*</members> &...


Top 50 recent answers are included