Test Matching in Data Logic: See Exactly Why a Record Didn't Match

When a record isn't updating the way you expect in the Data Logic module, tracking down the reason has always meant manually comparing field values against your Blueprint, row by row. It's slow, and the actual cause is often something small and easy to miss — a stray space, a hyphen where you expected a dash, a capitalization mismatch. Test Matching does that comparison for you and tells you, in plain language, exactly where things went wrong.

From Step 2: Input Mapping in the Data Logic module, after setting up the parameters, click Test Matching, search for and select the record you want to verify, and then click Evaluate. You'll get a full breakdown of both sides of your configuration:

• Input fields show whether each value matched a condition in your Blueprint, and if not, why.
• Output fields show whether they'll be updated, left alone, or filled with a fallback value, and why.

An Input Analysis and Output Analysis summary at the bottom gives you the takeaway at a glance, so you don't have to piece it together yourself. And if a record matches every input individually but still doesn't match overall, Test Matching flags that too, so you know a new Blueprint row is likely needed.

Test Matching also catches near-misses automatically. If an input value is almost identical to something already in your Blueprint, it calls out the specific difference — extra whitespace, a punctuation mismatch, a case difference — and tells you which Match Option would close the gap.

For example, if a record's Company Name is listed as "AT & T" but your Blueprint has "AT&T," Test Matching identifies the punctuation difference and recommends turning on Ignore Special Chars, rather than leaving you to spot the mismatch on your own.

Learn more: Module Overview: Data Logic