For batch jobs that perform cleansing, auto merging, matching, or validation, Trillium Quality for Dynamics processes data in sets. The batch sets created for a batch job are listed on the Batch Job window, as shown in the figure given below.
Some batch sets can be processed in parallel, some must be processed serially.
-
Cleansing can be processed in parallel because there is no dependency between records.
-
Auto Merge must run serially. Record #1 might be merging with record #3 and therefore record #2 cannot be merging with record #3 at the same time.
-
Matching can be run serially or in parallel. If multiple window keys are enabled, as they are in the default matching rules, batch sets will be processed serially due to the complex nature of multiple window key matching. However, if you have modified your matching rules to include only name and address matching (a single window key), batch sets will be processed in parallel, which improves performance.
The Execution Status column indicates which sets are waiting, processing and completed. Use the Page control (at the lower right of the batch set list) to see additional pages of batch sets.
To review details about each batch set, click the batch set name. The Batch Set Information window opens, displaying information about the processing of this set of records.
In the pre-defined batch requests, 10 records are processed in each batch set, and 20 batch sets are processed concurrently. These values minimize processing time for each set. Each batch set must complete processing under the two minute maximum set by Microsoft Dynamics 365. If processing exceeds two minutes, Microsoft Dynamics 365 will cancel further processing of that batch set. Depending on your system resources, you may gain processing speed by changing one or both of these settings, as described in Creating a Custom Batch Request.