Lists history records for Analytics dataflows 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.
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 | --dataflowid DATAFLOWID
Required
The ID of the dataflow to show history records.
Type: id
analytics:dataflow:history:revert (Deprecated)
Revert to a specified history record.
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.
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 | --dataflowid DATAFLOWID
Required
The ID of the dataflow to show history records.
Type: id
-y | --historyid HISTORYID
Required
The ID of the dataflow history record.
Type: id
-l | --label LABEL
Optional
Label for new reverted history record.
Type: string
analytics:dataflow:job:display (Deprecated)
Display the status of an Analytics dataflow job.
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.
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 | --dataflowjobid DATAFLOWJOBID
Required
ID of the dataflow job to display.
Type: id
analytics:dataflow:job:list (Deprecated)
Lists jobs for an Analytics dataflow.
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.
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 | --dataflowid DATAFLOWID
Required
ID of the dataflow to list the jobs for.
Type: id
analytics:dataflow:job:stop (Deprecated)
Stops an Analytics dataflow job.
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.
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 | --dataflowjobid DATAFLOWJOBID
Required
ID of the dataflow job to stop.
Type: id
analytics:dataflow:list (Deprecated)
Lists Analytics dataflows 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:dataflow:list
1sfdx analytics:dataflow:list
Command Syntax
sfdx analytics:dataflow: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:dataflow:start (Deprecated)
Starts an Analytics dataflow.
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.
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 | --dataflowid DATAFLOWID
Required
ID of the dataflow to start.
Type: id
analytics:dataflow:update (Deprecated)
Update an Analytics dataflow.
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.