Typical Batch Request Process - trillium_quality - 2.7

Trillium Quality for Dynamics Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Quality
Version
2.7
Language
English
Product name
Trillium Quality
Title
Trillium Quality for Dynamics Guide
Topic type
Administration
Overview
Installation
Reference
How Do I
Configuration
First publish date
2008
ft:lastEdition
2023-05-25
ft:lastPublication
2023-05-25T13:35:56.864032

To get the best results, you typically run batch jobs in a particular order, as follows:

  1. Run a cleanse request and review the results.

  2. Run a match request.

  3. If matches are found and you determine that there are duplicate records in your data, run an auto merge request.

A batch process must finish running before you run the next batch process.
Warning: Records must be cleansed before being matched or auto merged. The cleanse process creates the key on which matches are evaluated. If you run a Match Only process on records that have not been cleansed, no matches will be found.
Note: Standard batch requests are designed to process subsets of your data. Processing more than 10,000 records in a batch request is not recommended.