Skip to main content

When to use Joiner

Choose Joiner when you have two datasets that need to be connected through shared keys.

Joiner is most useful when one file contains the main records and another file contains context, attributes, or reference details that should be attached to those records.

Strong signs that Joiner is the right Tool​

Joiner is a strong fit when:

  • the information you need is split across two Files
  • both Files contain one or more Fields that should identify the same thing
  • you need selected Fields from both datasets in one output
  • you want to find Records that matched or did not match
  • the join logic should be saved and reused

Typical business situations​

Joiner is commonly used for situations like these:

Add reference fields​

Examples:

  • add product category to sales transactions
  • add department or region to employee records
  • add account owner to customer activity
  • add location metadata to operational files

Enrich a working file​

Examples:

  • attach customer names to account IDs
  • add status values from a source-of-truth export
  • add pricing tiers to a product list
  • combine event records with a participant list

Review match coverage​

Examples:

  • identify records in the main file with no lookup match
  • confirm that every transaction maps to a known account
  • find lookup records that were not used
  • investigate unexpected one-to-many or many-to-one relationships

Good fit vs poor fit​

Good fit​

Use Joiner when the goal can be described as:

  • "Add fields from this related file."
  • "Match these records using these keys."
  • "Show me which records connected successfully and which did not."

Poor fit​

Joiner is probably not the first Tool to use when:

  • the matching values are inconsistent and need cleaning first
  • duplicate records make the matching relationship unclear
  • you only need to filter one file
  • you need to calculate summaries rather than combine record-level fields

Ask this before you start​

Finish this sentence:

"I need to match this file to another file by ..."

If you can name the matching fields clearly, Joiner is often a good fit.

If you cannot, clarify the relationship between the datasets before building the configuration.

Start with match quality​

Before joining Files, inspect the key Fields.

Ask:

  • Are the key values present in both datasets?
  • Do they use the same format?
  • Are there leading zeros, spaces, punctuation, or capitalization differences?
  • Should each key match only one Record, or can it match several?

These questions shape the reliability of the join result.

Rule-of-thumb decision guide​

Use Joiner when the central task is combining related datasets.

Use another Tool first when the central task is cleaning match keys, deduplicating Records, filtering Records, or creating summary statistics.