Configuring match and merge
Configure the match and merge process to identify and resolve duplicate records. The match and merge process configuration together constitutes the match model. Based on the outcome of the match process and the merge configuration, the records are either automatically merged, queued for manual merge by a data steward, or skipped as not a candidate for merge.
The match process compares records to identify duplicates based on an exact or fuzzy match strategy. An exact match strategy identifies identical records, and a fuzzy match strategy identifies similar records. To configure the match and merge process, use the predefined match model or create a custom model to suit your business needs. You cannot edit the predefined model.
Important: You must configure and publish the match model after you configure the data model, but before the ingress job is run for the initial data load. If the match model configuration is published after the initial data load, the data that is already in the Business 360 data store is not indexed by the match model and does not undergo matching.
To configure the match model, perform the following tasks:
- 1. Review the predefined match model to determine whether the model meets your business requirements.
- 2. If the predefined match model does not meet requirements, configure a match model.
- 3. Configure declarative match rules for the match model to identify duplicate records and determine the merge action for these records.
- 4. Publish the match model.
After you publish a model, you can define match and merge jobs, and run the jobs. For information about defining and running match and merge jobs, see Define Jobs.