The Trillium Quality for Dynamics installation includes a console application that allows you to run a standard batch process from a command window. You can use the console application to run a batch request directly, bypassing the Standard Batch Manager. The benefit of using the console application is that you can start the batch requests automatically to streamline your daily processing.
To run the Trillium Quality for Dynamics console application
Open a command window as Administrator and navigate to your Trillium Quality for Dynamics bin directory.
At the command prompt enter the syntax as follows:
TSCrmMSD_StandardBatch_Console.exe <config_file> <batch_request_name> [status_file]
where:
config_file |
Required. The path and file name of the Standard Batch configuration file where the CRM connection information is stored. The pre-defined configuration files are located in your installation directory. For example, C:\Program Files \Trillium Software\TSQuality\17\TSCrmMSD\Batch. |
batch_request_name |
Required. The name of the batch request that is to be run. The list of names can be found under the TSS Batch Requests entity. Note: The name of the batch request must be enclosed by double quotation
marks.
|
status_file |
Optional. The name of the file where the status is being written to. If this argument is not used, then no status is written out. |
Example:
This is a sample command to run the batch request named TSS Cleanse Only [account].
TSCrmMSD_StandardBatch_Console.exe ..\Batch\BatchConfig.xml
"TSS Cleanse Only [account]" .\batchstatus.log
The following is an example of the status log file:
2019.02.01 17:12:32 *** Starting batch request ***
2019.02.01 17:12:32 Config file: ..\Batch\BatchConfig.xml
2019.02.01 17:12:32 Batch request name: TSS Cleanse Only [account]
2019.02.01 17:12:32 Loading config file
2019.02.01 17:12:32 Connecting to 10.65.100.10:80/ts251test
2019.02.01 17:12:35 Connection successful
2019.02.01 17:12:36 Last Scan:2/1/2019 5:12:36 PM
Batch Sets: Queued [1] In Process [0] Completed [0]
2019.02.01 17:12:42 Last Scan:2/1/2019 5:12:41 PM
Batch Sets: Queued [0] In Process [1] Completed [0]
2019.02.01 17:12:47 Last Scan:2/1/2019 5:12:47 PM
Batch Sets: Queued [0] In Process [1] Completed [0]
2019.02.01 17:12:52 Last Scan:2/1/2019 5:12:52 PM
Batch Sets: Queued [0] In Process [1] Completed [0]
2019.02.01 17:12:58 Last Scan:2/1/2019 5:12:58 PM
Batch Sets: Queued [0] In Process [1] Completed [0]
2019.02.01 17:13:03 Batch job completed