Skip to main content

Fusion — Lookup System (Multi-Value and Select-First-From-List)

Coming Soon — Fusion is in development and not yet available in production.

Status: Shipping June 2026

Fusion is currently in development and scheduled for release in June 2026. The information in this article reflects the planned design. Features and interface details may change before launch.

What Are Lookups?

A lookup is a translation table that converts a value from one system's vocabulary to another. When data flows from XactAnalysis into FileTrac (or any other paired system), the source and destination often use different codes, labels, or identifiers for the same concept. Lookups bridge this gap by defining explicit value-to-value mappings.

In Fusion, lookups are treated as first-class citizens — they have their own dedicated editing views, support annotations and comments, and can be reused across multiple transformations within a mapping.

Lookup Architecture

Dedicated Side Panel

Each lookup opens in its own side panel view within the Transformation Editor. The panel displays the full list of value pairs (source value on the left, destination value on the right) along with controls for adding, editing, and removing entries.

Comments and Annotations

Lookup entries support inline comments. This is particularly useful for documenting why a specific translation was chosen — for example, noting that a carrier uses a non-standard status code that requires special handling. Comments live within the lookup itself, keeping documentation co-located with the rule it describes.

Multi-Value Lookups

Standard lookups map one source value to one destination value. Multi-value lookups handle the more complex case where a single source field may need to produce multiple destination values, or where multiple source values should resolve to a single destination.

One-to-Many

A single source value maps to more than one destination value. For example, a combined "loss type and cause" code from an external system might need to populate both a "Loss Type" field and a separate "Cause of Loss" field in FileTrac.

Many-to-One

Multiple source values resolve to a single destination value. For example, several external status codes (such as "In Progress," "Under Review," and "Pending Adjuster") might all map to a single "Open" status in FileTrac.

Many-to-Many

In more complex scenarios, a set of source values maps to a set of destination values with conditional logic governing which combinations apply. Fusion's lookup editor supports these configurations with a matrix-style view that makes the relationships visible at a glance.

Select-First-From-List

When a multi-value lookup produces more than one possible match, Fusion needs a rule to decide which value takes priority. The Select-First-From-List pattern solves this by allowing administrators to define an ordered priority list.

How It Works

When a lookup returns multiple matching destination values, Fusion evaluates them against the priority list from top to bottom and selects the first match. This ensures deterministic, predictable results even when the data is ambiguous.

Example

Suppose a "Coverage Type" field from an external system returns three possible matches in the lookup table: "Wind," "Flood," and "Fire." If the administrator has configured the Select-First-From-List priority as Flood first, then Wind, then Fire — Fusion writes "Flood" to the destination field because it appears highest in the priority list.

Configuring Priority

The priority list is managed in a dedicated selection interface (documented in the Fusion design system as version 1.5). Administrators drag entries into their preferred order, and the list is saved as part of the lookup configuration. The priority order can be changed at any time without affecting the underlying value pairs.

Best Practices

  • Document your logic. Use the inline comment feature on any lookup entry that is not self-explanatory. Future administrators will benefit from knowing why a particular translation was chosen.

  • Review multi-value lookups carefully. One-to-many and many-to-many relationships can produce unexpected results if the priority order is not set intentionally. Always test with representative data before deploying to production.

  • Reuse lookups across transformations. If multiple field mappings use the same value translation (such as a common status-code table), reference the same lookup rather than duplicating it. This keeps your configuration consistent and easier to maintain.

Did this answer your question?