Skip to main content

Joiner examples

These examples show the kinds of business problems Joiner can help solve.

Example 1: Add product categories to sales transactions​

A sales file contains product codes, quantities, and amounts. A separate product reference file contains product names, categories, and business units.

Use Joiner to match the sales file to the product reference file by product code and add category fields to the sales output.

Why Joiner fits

The task is not to clean or filter the Records. The main need is to attach Fields from a related dataset using a shared key.

Example 2: Attach account owners to open cases​

A support case export includes account IDs but not account owners. A separate account file lists the owner and region for each account.

Use Joiner to add owner and region to the case file so the support team can route follow-up work.

Why Joiner fits

The case Records already exist, but important context lives in another File. Joiner makes the relationship repeatable.

Example 3: Match payments to an approved vendor list​

A payment file contains vendor IDs. An approved vendor list contains vendor IDs, names, and approval status.

Use Joiner to identify which payments match approved vendors and which payments need review.

Why Joiner fits

The result depends on matching Records across datasets and reviewing unmatched or unexpected Records.

Example 4: Add location details to operational records​

An operations file includes site codes. A location reference file includes site names, regions, and managers.

Use Joiner to add descriptive location fields before reporting.

Why Joiner fits

The join enriches the main dataset without changing which Records exist.

Example 5: Find records with no lookup match​

A customer activity File should match every account ID to the account master. Some Records do not match.

Use Joiner to produce a result that highlights unmatched account IDs for investigation.

Why Joiner fits

Joiner is useful not only for successful matches, but also for revealing where expected relationships are missing.

Practical pattern​

For each Joiner use case, define:

  • the primary dataset
  • the secondary dataset
  • the key Fields
  • the Fields to add
  • how unmatched Records should be reviewed

If those pieces are clear, you are usually ready to build a Joiner configuration.