New answers tagged

0

sometimes you will need to upgrade the Sforce extn pack or the sf CLI to the latest version. just uninstall the extensions and install again. also you need to create project manifest.


1

As of v49.0, there are now force:community commands in sfdx! Salesforce CLI Command Reference: community Commands


0

I have similar setup in Azure DevOps and here is how it looks like - You can have your own folder structure but make sure to map ant-salesforce.jar & build.properties in your build.xml. Also, when you run your CI/CD point to folder containing build.xml.


0

Depends on what files you're talking about, what org you're working against, and how much the org matches your source (if it's not a scratch org). If you're utilizing scratch orgs, you can use sfdx force:source:push to sync those changes to the scratch org. If you feel it's gotten messy - you can also discard it and spin up a new one with your local as the ...


0

I removed this part from the sfdx-project.json file { "path": "force-app", "default": true, "package": "dreamhouse", "versionName": "ver 1.0", "versionNumber": "1.0.0.NEXT" }, And it worked . **One ...


1

I worked with a colleague on this. The answer was to create the new package version as 1.1.0-1. For some reason, using 1.0.3.0 was not accepted. Having the beta version number be something other than zero was the answer.


0

Salesforce development does not produce externalizable artifacts other than source code. You can, of course, use any applicable tool you wish to managed releases of your source code, but there's no packaging or compilation process you can apply off-platform. You may choose to practice the Package Development Model to produce on-platform packages that can be ...


5

It stands for the default scratch org username. A (U) on the left points to the default scratch org username. The default Dev Hub and scratch orgs are marked on the left with (D) and (U), respectively. Source.


0

I got this problem while trying to authorize while doing trailhead challenges so there is no production, and test.salesforce.com somehow is not working. If you are already logged in and don't want to log out to get the domain info, you can use Domains section from Setup menu and get the info from there to authorize your org.


0

If it's windows try going to settings -> Network & internet -> poxy and turn off auto select. Nothing else that I found worked, but I found a solution here. https://github.com/forcedotcom/salesforcedx-vscode/issues/1818


0

This appears to be the same error as this post Have you tried the approaches mentioned in https://success.salesforce.com/answers?id=9063A000000pwoMQAQ i.e., Installing the x64 version of the CLI and changing the PATH environment variable to point to that Rename and move "Salesforce CLI" folder to a path without space in its name Open visual studio code as ...


2

As in everything, the key is reading the authorization documentation closely If you happened to be logged into that scratch org from some other tool or browser, you note that the URL for that org will look like: Lightning: https://xxx-yyy-zzz-dev-ed.lightning.force.com/... Classic: https://xxx-yyy-zzz-dev-ed.cs68.my.salesforce.com/ The doc clearly states ...


0

I was trying to Authorize my Org and got below message: ERROR running force:auth:web:login: grant type not supported I am running windows 10 and when I turned off my firewall and tried again the authorization worked. I hope that helps someone.


Top 50 recent answers are included