As of April 20, 2023, we no longer maintain this section of the command reference. Refer to the reference information about the sf-style commands instead, which we update regularly. We keep this reference information about the sfdx-style commands as-is for historical reference only.
The sfdx-style commands continue to work the same as before, and any scripts that use the commands won’t break. However, we recommend that you start using the equivalent sf-style commands.
The reference page for each sfdx command has been updated with information about its equivalent sf command. The page also shows how the flag names have changed between the sfdx and sf commands. Use this information to migrate your scripts.
For background information about this change, read this blog post, which describes how we’ve updated many of the existing sfdx commands to use the improvements we made in sf commands. To view all the changes, read the CLI release notes starting with version 7.183.1 on January 12, 2023.
Warning
Examples for analytics:dataset:display
1sfdx analytics:dataset:display -i datasetId
1sfdx analytics:dataset:display -n datasetApiName
Command Syntax
sfdx analytics:dataset:display
[--json]
[--loglevel LOGLEVEL]
[-u TARGETUSERNAME]
[--apiversion APIVERSION]
[-i DATASETID]
[-n DATASETNAME]
Parameters
--json
Optional
Format output as JSON.
Type: boolean
--loglevel LOGLEVEL
Optional
The logging level for this command invocation. Logs are stored in $HOME/.sfdx/sfdx.log.
A username or alias for the target org. Overrides the default target org.
Type: string
--apiversion APIVERSION
Optional
Override the API version used for API requests made by this command.
Type: string
-i | --datasetid DATASETID
Optional
Dataset ID.
Type: id
-n | --datasetname DATASETNAME
Optional
Dataset api name.
Type: string
analytics:dataset:list (Deprecated)
Lists Analytics datasets in the specified target org.
As of April 20, 2023, we no longer maintain this section of the command reference. Refer to the reference information about the sf-style commands instead, which we update regularly. We keep this reference information about the sfdx-style commands as-is for historical reference only.
The sfdx-style commands continue to work the same as before, and any scripts that use the commands won’t break. However, we recommend that you start using the equivalent sf-style commands.
The reference page for each sfdx command has been updated with information about its equivalent sf command. The page also shows how the flag names have changed between the sfdx and sf commands. Use this information to migrate your scripts.
For background information about this change, read this blog post, which describes how we’ve updated many of the existing sfdx commands to use the improvements we made in sf commands. To view all the changes, read the CLI release notes starting with version 7.183.1 on January 12, 2023.
Warning
Examples for analytics:dataset:list
1sfdx analytics:dataset:list
Command Syntax
sfdx analytics:dataset:list
[--json]
[--loglevel LOGLEVEL]
[-u TARGETUSERNAME]
[--apiversion APIVERSION]
Parameters
--json
Optional
Format output as JSON.
Type: boolean
--loglevel LOGLEVEL
Optional
The logging level for this command invocation. Logs are stored in $HOME/.sfdx/sfdx.log.
A username or alias for the target org. Overrides the default target org.
Type: string
--apiversion APIVERSION
Optional
Override the API version used for API requests made by this command.
Type: string
analytics:dataset:rows:fetch (Deprecated)
Fetch the rows of an Analytics dataset.
As of April 20, 2023, we no longer maintain this section of the command reference. Refer to the reference information about the sf-style commands instead, which we update regularly. We keep this reference information about the sfdx-style commands as-is for historical reference only.
The sfdx-style commands continue to work the same as before, and any scripts that use the commands won’t break. However, we recommend that you start using the equivalent sf-style commands.
The reference page for each sfdx command has been updated with information about its equivalent sf command. The page also shows how the flag names have changed between the sfdx and sf commands. Use this information to migrate your scripts.
For background information about this change, read this blog post, which describes how we’ve updated many of the existing sfdx commands to use the improvements we made in sf commands. To view all the changes, read the CLI release notes starting with version 7.183.1 on January 12, 2023.