@futurefirst/sfdx-plugin-picklist
v0.0.1
Published
SFDX CLI plugin to manipulate picklist values
Downloads
47
Maintainers
Readme
@futurefirst/sfdx-plugin-picklist
SFDX CLI plugin to manipulate picklist values
$ npm install -g @futurefirst/sfdx-plugin-picklist
$ sfdx COMMAND
running command...
$ sfdx (-v|--version|version)
@futurefirst/sfdx-plugin-picklist/0.0.1 linux-x64 node-v10.17.0
$ sfdx --help [COMMAND]
USAGE
$ sfdx COMMAND
...
sfdx picklist:list -s <string> -f <string> [-r <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
list values for a picklist field
USAGE
$ sfdx picklist:list -s <string> -f <string> [-r <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
OPTIONS
-f, --fieldname=fieldname (required) the name of the picklist
field whose values you want to list
-r, --resultformat=human|csv|json [default: human] result format
emitted to stdout; --json flag
overrides this parameter
-s, --sobjecttype=sobjecttype (required) the sObject type with the
picklist field
-u, --targetusername=targetusername username or alias for the target
org; overrides default target org
--apiversion=apiversion override the api version used for
api requests made by this command
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
EXAMPLE
$ sfdx picklist:list -u [email protected] -s Opportunity -f My_Custom_Field__c
Debugging your plugin
We recommend using the Visual Studio Code (VS Code) IDE for your plugin development. Included in the .vscode
directory of this plugin is a launch.json
config file, which allows you to attach a debugger to the node process when running your commands.
To debug the hello:org
command:
- Start the inspector
If you linked your plugin to the sfdx cli, call your command with the dev-suspend
switch:
$ sfdx hello:org -u [email protected] --dev-suspend
Alternatively, to call your command using the bin/run
script, set the NODE_OPTIONS
environment variable to --inspect-brk
when starting the debugger:
$ NODE_OPTIONS=--inspect-brk bin/run hello:org -u [email protected]
- Set some breakpoints in your command code
- Click on the Debug icon in the Activity Bar on the side of VS Code to open up the Debug view.
- In the upper left hand corner of VS Code, verify that the "Attach to Remote" launch configuration has been chosen.
- Hit the green play button to the left of the "Attach to Remote" launch configuration window. The debugger should now be suspended on the first line of the program.
- Hit the green play button at the top middle of VS Code (this play button will be to the right of the play button that you clicked in step #5). Congrats, you are debugging!