In addition to providing the parameters required for the import or export commands, you can append commands with these optional commands:
Table 23. Optional Command Line Arguments
Command | Description |
|---|---|
–c configfile | Path to the configuration file |
–l logfile | Path to the log file that records unexpected errors |
-e failedRecordsLogs | Path to the log file for failed records and describes events that prevented records from being read or written Default file is failedRecords.log |
–i successfulRecordsLog | Path to the log file for all successful records .By default, this log is not written due to size. If required, you can set this log in the configuration file |
–o outputfile | For import—Path to the output file where error records are written |
–q queryfile | For export—File containing the query information to determine which records to export. If blank, all records are exported |
–m mapping | Path to the mapping file, that defines the format of the expected CSV file. The mapping file only requires information about one behavior, so is useful if your input files are in a slightly different but compatible format The configuration file points to the mapping file, but may be overridden by this option. |
–d date format | Date format. This setting overrides the format defined in the configuration file |
–n number format | Number format. This setting overrides the format defined in the configuration file |
–cp codepage | Code page to use when reading or writing the CSV file. This option overrides the configuration file setting |
–u username | The Performance Scorecard user name. This option overrides the configuration file setting |
–p password | The Performance Scorecard password to log on to the application. This option overrides the configuration file setting |
–domain domain | NTLM domain |
–nolock | Do not try to obtain business object locks before updating or deleting Caution! Do not use this option there are other current users |
–v config file option | Defines a configuration file or custom option. For example: –v rowTransactions=false is the same as setting rowTransactions=false in the configuration file. |