Cloud Portal ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (16.2.0) 16.1.0 16.0.0 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
User Community Service Desk Downloads

Configure Advanced Matching

This article describes how to configure advanced matching scenarios, including multiple matching operations and specialized matching configurations that go beyond the standard matching setup.

Before you start

Advanced matching configuration is used when you need more sophisticated matching logic than the standard single matching operation provides, such as:

  • Multiple matching operations on the same entity (for example, matching unique people vs unique households).

  • Custom matching step configurations with specialized rules.

  • Complex rematch conditions and matching override scenarios.

Before configuring advanced matching, ensure you understand:

How to configure advanced matching

To configure advanced matching, you can:

Use the default Matching step and an additional matching configuration

This allows you to add custom matching logic while saving time by reusing preset attributes, making it suitable for most use cases.

To set it up:

  1. Configure advanced matching on entity.

    1. Configure rematch conditions using Single Matching step rematch configuration.

  2. Apply advanced matching to entities.

Use multiple custom Matching steps

This turns off default matching entirely, giving you complete control including custom naming conventions.

However, such level of granularity is rarely needed. Instead, consider configuring a custom Matching step in addition to the default one.

To set it up:

  1. Configure advanced matching on entity.

    1. Configure rematch conditions using Global rematch configuration.

  2. Apply advanced matching to entities.

Configure advanced matching on entity

In ONE Desktop, open your MDM project and navigate to Logical Model > Instance Layer. Find and double-click your entity.

In the entity properties, switch to the Matching tab. Scroll down to Advanced Matching Configuration and select composite element next to it.

Enable advanced matching on entity

In Core Matching Columns Definition, define the columns for your additional matching operation.

Advanced matching configuration - Map core matching columns

  • Name: The name of the Matching step.

  • Master Id Column: The ID for matching groups.

  • Match Rule Name Column: The name of the first successful matching rule.

  • Match Quality Column: The strength of the match, expressed as a number between 0 and 1, where 0 is a perfect match.

  • Match Related Id Column: The ID of the record to which another record was matched to.

  • Isolate Flag Column: The Boolean value for isolate. Records with the isolate flag set to true are excluded from matching.

  • Rematch Flag Column: The Boolean value for rematch. Records with the rematch flag set to true are included in the next rematch operation.

  • Proposals (Boolean): If enabled, the MDM Engine generates another Integration Output in the matching plan to accept the pairs of proposed records (based on the defined rules).

  • Rematch If Changed Columns: See Configure rematch conditions.

Turn off default matching (optional)

If you want to use only custom Matching steps, select Disable Default Matching Definition in the Advanced Matching Configuration.

This is typically used when you need complete control over the matching process or when default matching doesn’t meet your requirements.

Advanced matching configuration - Default matching definition turned off

Configure rematch conditions

For a refresher on the basics of and different approaches to rematching, see Rematching.

Rematch conditions define when records should be re-evaluated for matching based on data changes. If any attribute in the column changes, the rematch flag for that matching will be set to true.

For example, if you have a golden entity 'party' and silver entity 'address' (that is, matching of 'address' is done by party_master_id), a change of master_id on 'party' will not be propagated to the relevant address records. To ensure it is propagated, you need to define rematch conditions for each new Matching step.

For the default Matching step, rematch conditions are already predefined, although you can add additional conditions if needed. See Configure additional rematch conditions for the default Matching step.

Only columns of origin source, clean, copy_source, and copy_clean can be used to trigger rematch.

These conditions can be configured in one of two ways:

  • If you’re using the default Matching step: By defining Core Matching Columns Definition in the entity Advanced Matching Configuration.

  • If you’re using multiple Matching steps: By defining Rematch If Changed Section in the entity Advanced Matching Configuration. This determines columns in which changes will trigger rematch in all or selected Matching steps.

Single Matching step rematch configuration

For individual Matching step configurations:

  1. In the entity Advanced Matching Configuration, in Core Matching Columns Definitions, double-click the corresponding row number. This opens the advanced Matching step properties.

    Advanced matching configuration - Advanced matching step properties

  2. Find Rematch If Changed Columns and select list element next to it.

  3. Define the column names where changes should trigger rematch.

    Advanced matching configuration - Rematch If Changed configuration
To define rematch conditions for the 'party' entity, use Global rematch configuration instead.

Global rematch configuration

To define rematch columns for multiple Matching steps:

  1. In the entity Advanced Matching Configuration, in Rematch If Changed Section, define the desired columns.

  2. Define where you want these conditions to be applied:

    • In all configured Matching steps: Select Use for All Matchings. Otherwise, leave the field clear.

    • In selected Matching steps: Configure Rematch If Changed Matchings Node.

      1. Double-click the Rematch If Changed Matchings Node element and then select edit element to expand.

        Advanced matching configuration - Rematch If Changed matchings node

      2. Select Fill Columns and choose from the available Matching steps.

        Rematch If Changed configuration - map steps

Configure additional rematch conditions for the default Matching step

Using the same configuration options as described in Global rematch configuration, you can also define additional rematch conditions for default matching. For example, default matching on the address entity has party_master_id predefined in Rematch If Changed Columns on the entity Matching tab.

To add additional columns for rematch, define these columns in Advanced Matching Configuration > Rematch If Changed Section.

For each column, in Rematch If Changed Matchings Node, make sure to select the repository k.

Apply advanced matching to entities

After configuring advanced matching on the entity level, you need to make sure it’s used during processing.

Configure repository names

Open your matching plan and double-click the Matching step.

On the General tab, enter a Repository Name:

  • For default Matching step: Always use k.

  • For custom Matching steps: The matching name defined in Name in the entity Advanced Matching Configuration.

Matching step - Configure repository name

Configure custom grouping

In your MDM project, navigate to Logical Model > Master Data Layers. Find and double-click your golden entity.

On the Advanced Settings tab, set Custom Grouping Column:

  • For default Matching step: Must be master_id.

  • For custom Matching steps: The column defined in Master Id Column in the entity Advanced Matching Configuration. See Configure advanced matching on entity.

Golden entity Advanced Settings - Configure Custom Grouping Column

Next steps

After configuring advanced matching:

Was this page useful?