Here are the new and changed features in recent updates of Salesforce CLI and the salesforcedx plug-in.
Run sfdx version to display the version of Salesforce CLI installed on your computer. Run sfdx plugins --core to display the version of the installed salesforcedx plug-in.
Run sfdx update to update both the CLI and the salesforcedx plug-in to the latest available version.
Click here for the v46 release notes.
force:config:set disableTelemetry=true or set the SFDX_DISABLE_TELEMETRY environment variable to true.-x parameter with force:source:retrieve, static resources are retrieved correctly.force:apex:execute with the JSON flag (--json) displays the correct output.NEW: When running force:mdapi:deploy, force:source:deploy, or force:source:push, we display a progress bar to highlight the start and completion of the command.
NEW: We've added a --checkonly | -c parameter to the force:source:delete command. This parameter allows you to validate your source:delete before deleting metadata.
NEW: We've released a new autocomplete feature. Once installed, you can type a command and then press Tab to autocomplete a partially typed command, or press Tab to see all the available commands. If there are no matching commands or parameters to return, pressing Tab autocompletes the file path in your current directory.
Note: Autocomplete is not currently available on Windows.
To install this feature, follow these steps:
sfdx plugins:install @oclif/plugin-autocomplete.sfdx autocomplete, then follow the displayed instructions.NEW: We've added a new command, force:analytics:template:create, which allows you to create a simple analytics template in a specified directory.
CHANGE: Commands run against a scratch org complete successfully regardless of the location of the JWT key file (server.key) used to authorize the Dev Hub org.
FIX: Running force:apex:test:run with or without a JWT key file (server.key) works as expected.
FIX: When updating the CLI to the latest version, you no longer see a MaxListernersExceededWarning message.
FIX: When running force:source:deploy, static resource zip files are automatically deleted from the temp directory.
We aren't releasing a Salesforce CLI patch this week.
We aren't releasing a Salesforce CLI patch this week.
We aren't releasing a Salesforce CLI patch this week.
force:source:deploy, you can specify the name of a CustomLabel within the package manifest.force:config:set command displays the correct error message in Salesforce Extensions for VS Code.force:mdapi:convert --metadata, you can now pass a comma-separated list of metadata types.We aren't releasing a Salesforce CLI patch this week.
We aren't releasing a Salesforce CLI patch this week.
sfdx force:project:create.sourceApiVersion in the sfdx-project.json file is now the same as the CLI version.salesforcedx-templates to address security issues.--componentname parameter for the lightning:app:create and visualforce:component:create commands follows the Lightning web component naming conventions. It uses lower camel case for component file names and upper camel case for JavaScript class names.sfdx force:source:pull command supports the Workflow metadata type.force:project:create, project names can include special characters. To use a reserved character in the project name, surround the project name in quotation marks:
sfdx force:project:create -n "test&project"
sfdx force:project:create -n "\\testproject?"
CHANGE: Due to framework changes in the salesforcedx plug-in, the -a short version of the --apiversion parameter is no longer available for these commands:
force:apex:class:createforce:apex:trigger:createforce:lightning:app:createforce:lightning:component:createforce:lightning:event:createforce:lightning:interface:createforce:visualforce:component:createforce:visualforce:page:createFIX: When an alias for a username exists, running force:auth:list displays the username and the alias. If no alias exists, the command returns only the username.
FIX: When deploying metadata to an org, running force:mdapi:deploy with the validateddeployrequestid option now completes without errors.
force:source:convert and force:mdapi:convert commands: -x | --manifest, -m | --metadata, and -p | --sourcepath.We didn't release a CLI patch this week.
Welcome to the first release of version 47 of the salesforcedx plug-in for Salesforce CLI in Winter '20. Here's what's changed:
force:org:create command encounters signup errors, Salesforce CLI no longer hangs.force:org:create command encounters problems with streaming, it fails over to the polling client, and the command timeout default (or the --wait parameter value) is now honored.source:pull and source:status recognize the remote changes.sfdx force:source:retrieve -x package.xml or sfdx force:source:retrieve -m Dashboard:Dashboard_Folder/Dashboard_Name to retrieve your dashboard. If you plan to retrieve using a manifest, make sure to add dashboards to your package.xml.force:source:delete deletes an entire directory. To delete an individual file, delete it from your local DX project, then use force:source:push (for scratch orgs) or force:source:deploy to update the static resource in the target org.force:project:create.We're still working on creating salesforcedx v47 installers. However, you can easily update Salesforce CLI to v47 by running sfdx update or any CLI command. If you are installing Salesforce CLI for the first time, see Install Salesforce CLI to install the CLI for your operating system, then run sfdx update.
salesforcedx CLI Plug-InIf you installed the pre-release version 47 of the salesforcedx plug-in, uninstall it, then run the update command.
sfdx plugins:uninstall salesforcedx
sfdx update
These new commands are now available in salesforcedx v47 (beta).
force:package:hammertest:list: Lists the statuses of running and completed ISV Hammer tests.
force:package:hammertest:report: Returns the status of a running ISV Hammer test or the results of a completed hammer test.
force:package:hammertest:run: Runs ISV Hammer for the specified package version and subscriber orgs.
Note: As a beta feature, ISV Hammer is a preview and isn’t part of the “Services” under your master subscription agreement with Salesforce. Use this feature at your sole discretion, and make your purchase decisions only on the basis of generally available products and features. Salesforce doesn’t guarantee general availability of this feature within any particular time frame or at all, and we can discontinue it at any time. This feature is for evaluation purposes only, not for production use. It’s offered as is and isn’t supported, and Salesforce has no liability for any harm or damage arising out of or in connection with it. All restrictions, Salesforce reservation of rights, obligations concerning the Services, and terms for related Non-Salesforce Applications and Content apply equally to your use of this feature. You can provide feedback and suggestions for this feature in the ISV Hammer group in the Trailblazer Community.
These new commands are available in salesforcedx v47.
force:auth:device:login(beta). You can authorize an org using a device code. This means that you can use Salesforce CLI to authenticate in a Docker container or any headless environment without setting up JWT. For more information, see OAuth 2.0 Device Authentication Flow in Salesforce Help or Remote Development in the Salesforce Extensions for Visual Studio Code User Guide.
Note: The force:auth:device:login command is in beta and has been released early so we can collect your feedback. It may contain significant problems, undergo major changes, or be discontinued. If you encounter any problems, or want to request an enhancement, open a GitHub issue. The use of this feature is governed by the Salesforce.com Program Agreement.
These parameters are new in salesforcedx v47.
force:package:hammertest:run --apextestinterface | -n (beta). After upgrade validation, runs the Apex tests in the subscriber org that implement this interface.
force:package:version:create. We added several parameters to this command:
| Parameter | Description |
|---|---|
--codecoverage | Calculates and stores the code coverage percentage by running the Apex tests included in the package version. To promote a new managed package version to the released state, the code coverage minimum must be met. |
--postinstallscript | For managed packages only, specifies an Apex script to run automatically in the subscriber org after the managed package is installed or upgraded. |
--postinstallurl | Specifies a URL to post-install instructions for subscribers. |
--releasenotesurl | Specifies a URL to release notes. |
--uninstallscript | For managed packages only, specifies an Apex script to run automatically in the subscriber org before the managed package is uninstalled. |
The functionality for these commands changed in weekly releases of salesforcedx v46 or in the pre-release of v47.
force:org:delete -u MyDevSandbox. Deleting a sandbox created by the CLI is now supported.
force:package:install --securitytype | -s. We changed the default value changed from AllUsers to AdminsOnly.
force:source:status, force:source:push, force:source:pull. Source tracking is supported for Einstein Bots metadata in scratch orgs.