Skip to main content

Run Joiner

After you have selected the input datasets and Configuration, you are ready to run Joiner.

A successful Joiner Run should produce a merged result that makes business sense, not just a completed status.

Typical run steps​

A typical Run looks like this:

  1. open Joiner
  2. select the primary dataset
  3. select the secondary dataset
  4. choose the Joiner configuration
  5. review the match keys and output fields
  6. start the Run
  7. inspect matched and unmatched Records
  8. confirm the result is ready for the next step

What to check before you run​

Before starting the Run, verify:

1. The correct datasets are selected​

Confirm that both Files are the intended versions.

Check items such as:

  • reporting period
  • source system export
  • business unit or operating context
  • File freshness
  • whether either File is a draft or sample

2. The configuration matches the current purpose​

Make sure the selected Configuration uses the right keys and output Fields for this workflow.

This matters when your team has several similar configurations for different departments, reporting periods, or downstream systems.

3. You know what match success should look like​

Before the Run begins, decide how you will review the result.

Examples:

  • most primary Records should have a match
  • certain known examples must match
  • certain Records are expected to remain unmatched
  • unmatched Records should be reviewed before the output is shared

Review the result after the run​

After processing finishes, review:

  • matched Records with expected secondary Fields
  • primary Records with no match
  • secondary Records that may not have been used, if relevant
  • Records with blank or unusual keys
  • any repeated-key situations that could affect the output

Do not rely only on Record count. Spot-checking known examples is usually more informative.

If matches are missing​

When expected matches are missing, investigate one example at a time.

Common causes include:

  • leading or trailing spaces
  • different capitalization or punctuation
  • missing leading zeros
  • different ID formats across systems
  • duplicate keys in one of the datasets
  • the wrong File version or Configuration

If the issue is source formatting, clean the keys first and rerun the join.

If too many records matched​

Unexpectedly broad matches may mean the key is not specific enough.

Review whether:

  • one key should be combined with another key
  • duplicate Records need to be resolved first
  • the secondary File contains multiple valid matches per key
  • the Configuration is using the intended Fields

Final checkpoint before downstream use​

Before exporting, sharing, or passing the result to another process, confirm:

  • the correct datasets were used
  • the intended configuration was run
  • matched and unmatched Records were reviewed
  • the output Fields are useful and understandable
  • the result supports the business purpose