Custom Table Deep Dive: Data Lookup Matcher

[Jake Gillespie]

In complex enterprise environments, there is often a need to match one set of values against another to facilitate a workflow or business process. For example, matching an option selected on a catalogue request form to the applicable assignment group. It can be tempting to hardcode these intricate data correlations into the workflow logic, or even into a script. In such situations, the Data Lookup Matcher Table emerges as a powerful (and scalable) architectural solution. Following on from my previous article Custom Tables: Where and when to build, we'll now deep-dive into how and why Data Lookup Matcher Tables are so powerful.

Custom Table Disclaimer

The creation and usage of custom tables is directly tied to ServiceNow subscription entitlements. The articles I've written in relation to custom tables are based on the ServiceNow Custom Table Guide, which is available via the Legal Schedules -> Entitlement Supplements page. I strongly recommend seeking guidance from the ServiceNow Accounts team as licensing rules, entitlement SKUs, and specific limits can change over time. At the time of writing, this version became effective October 17, 2025.

What Exactly Are Data Lookup Matcher Tables?
A Data Lookup Matcher Table is a specialised type of custom table designed to facilitate complex lookups across different datasets within your ServiceNow instance. Architecturally, these tables are extended from the Data Lookup Matcher [dl_matcher] table. They act as an intermediary mechanism, allowing you to define and manage specific matching criteria between two or more data sources without having to hardcode the relationships. By default, records managed in these tables are captured to Update Set, making them easier to deploy alongside the workflow logic they support.

The Architectural Advantage: Why Use Lookups?
The primary benefit of using a Data Lookup Matcher Table is its ability to provide a flexible, performant bridge for complex querying. Instead of relying on brittle, hardcoded joins or writing extensive custom scripts every time you need to correlate data, the matcher table allows you to define the relationship once and reuse that logic across various parts of your application.

The Exempt Status: A Licensing Consideration
It is important to note that Data Lookup Matcher Tables are classified as Exempt Tables, as per the ServiceNow Custom Table Guide. This means they are customer-created tables that do not count against your overall Custom Table usage limit. This exemption is granted because the functionality (the ability to facilitate complex data correlation and lookup) is deemed essential for maintaining system flexibility within the platform. These tables typically have a low record count when compared with tables such as Tasks, Cases, and Requests.

When to use a Data Lookup Matcher Table

• Frequent Relationship Changes: When data relationships are likely to change often and therefore should not be hardcoded into scripts or workflow logic.
• Complex Relationship Mapping: For situations where the relationship between two entities is not a simple one-to-many or many-to-many, but requires matching on multiple criteria simultaneously (e.g., matching based on both 'Region' AND 'Product Line').
• Application Administration: When members of a business unit want to manage their own lookup data, they can be given table access via roles, allowing them to make changes directly without needing to burden the development team or waiting for a whole release cycle.

In essence, Data Lookup Matcher Tables are not merely storage; they are powerful but simple tools that enable developers to build highly robust, flexible, and scalable solutions by allowing precise correlation between otherwise isolated pieces of information within the ServiceNow ecosystem.