Pair Coverage Validation

Pair Coverage Validation

MatchLogic enforces a coverage rule to ensure that no datasource is accidentally excluded from the matching process. This validation runs automatically whenever you modify your pair configuration.

Match Configuration page showing a coverage validation error with an uncovered datasource highlighted and the Save and Continue button disabled

Match Configuration page with all datasources covered by at least one enabled pair, showing the Save and Continue button enabled and ready

The Coverage Rule

Every imported datasource in your project must participate in at least one enabled pair configuration. This means each datasource must appear as either the source or the target (or both) in at least one checked pair. If any datasource is not covered by any active pair, MatchLogic considers the configuration incomplete.

What Happens When Coverage Fails

When one or more datasources are not included in any enabled pair:

  1. The Save & Continue button is disabled. You cannot proceed to Match Definitions until the issue is resolved.
  2. The uncovered datasources are highlighted in the interface so you can quickly identify which sources need attention.
  3. A validation message appears explaining that all datasources must be covered.

Why This Matters

Without this safeguard, you could accidentally skip an entire datasource during matching. Records in the excluded datasource would never be compared to anything, meaning duplicates involving those records would go undetected. The coverage validation prevents this oversight.

How to Fix Coverage Issues

To resolve a coverage failure, you have several options:

  • Enable an existing pair — check the box next to a pair that includes the uncovered datasource. This is usually the quickest fix.
  • Change your strategy — switching to Find All Duplicates (see https://help.matchlogic.io/article/250-selecting-a-matching-strategy) generates all possible pair combinations, including within-file pairs, which guarantees every datasource is covered.
  • Remove the datasource — if the datasource was imported by mistake or is not relevant to this matching project, you can remove it from the project via the https://help.matchlogic.io/article/251-configuring-datasource-pairs page. Once removed, it no longer needs coverage.

Tip

If you are unsure why a datasource is uncovered, switch to the network diagram view (https://help.matchlogic.io/article/252-using-the-network-diagram). Isolated nodes with no connecting lines represent uncovered datasources.

Important

Coverage validation checks that every datasource is in at least one pair — it does not verify that your pairs form a fully connected graph. Two separate clusters of datasources are valid as long as each individual source is covered.

Common Scenarios

  • Three datasources, only two paired — the third datasource is uncovered. Add a pair that includes it.
  • Cross-File strategy with an odd datasource — if you have an odd number of sources and only pair some of them, the remaining source will be flagged. Consider adding a within-file pair for it.
  • All pairs unchecked for one source — if you disabled all pairs involving a particular datasource, re-enable at least one.