Advanced Search Showing Stale Facet Values After RDM Canonical Value Rename

Symptom

After renaming a canonical value in RDM (for example, renaming "ABN Number" to "ABN/ACN/NZBN Number"), the Advanced Search facet continues to display the old value alongside — or instead of — the new canonical value. Affected records appear under the stale facet entry even though the profile UI and raw JSON reflect the updated value.

Running a standard Reindex (Entity) or Reindex for RDM alone does not clear the stale facet.

Additionally, affected entities may display a lookup error in their JSON:

{
  "value": "RDM Value",
  "lookupError": "1003: RDM canonical value mapping not found for value [RDM Value] and source [Source] in tenant [<rdm-tenant-id>]"
}

This issue has two contributing factors that must both be addressed:

Incomplete source mappings in RDM

When a canonical value is renamed, the source value mappings for each source system (for example, Oracle EBS, Salesforce, Reltio) must also be updated to point to the new canonical name. If the Value field on any source mapping still references the old canonical name, the transcoding lookup fails and the platform surfaces the raw unmapped value in the search index.

Unmapped source codes appear in the Unmapped Values panel on the RDM Mapping tab. Any code listed there will produce a 1003 error on entities carrying that value.

Stale search index entries

Even after the RDM mapping is corrected, the MDM tenant's in-memory RDM transcode cache continues to serve the old mapping for up to 10 minutes. Records with 1003 lookup errors persist in the search index until a targeted reindex is run.

Resolution

Complete the following steps in order.

Step 1 — Fix the RDM Source Mapping

1. Navigate to the affected RDM tenant and open the relevant lookup type
2. Go to the Mapping tab
3. Open the Unmapped Values panel — any source codes not yet mapped to a canonical value appear here, grouped by source system
4. For each unmapped code that should resolve to the renamed canonical value:
   • Drag the source code card and drop it onto the correct canonical row on the left
   • After dropping, click into the newly mapped entry
   • Confirm the Source Code field (top) contains the source system's literal identifier — leave this unchanged
   • Update the Value field (bottom) to the new canonical value name.
   • This step is critical — dropping the card alone is not sufficient. The Value field must be manually set to the new canonical name; otherwise, the 1003 error will persist
5. Repeat for all source systems with unmapped codes related to this rename
6. Click Save and wait for the save confirmation

Important: Check all source systems in the Unmapped Values panel, not just the one that triggered the initial issue. In a typical rename scenario, Oracle EBS, Salesforce, and Reltio source entries may each require separate mapping updates.

Step 2 — Reset the RDM Transcode Cache

Note: This step requires Reltio Customer Engineering or Support access. Raise a support ticket to request this action, or wait up to 10 minutes for the cache to refresh automatically before proceeding to Step 3.

POST https://<environment>.reltio.com/reltio/resetRDMCache

No request body is required. This forces the MDM tenant to immediately pick up the updated RDM mapping rather than serving stale cached values.

Step 3 — Reindex Unresolved RDM Lookups

This targeted reindex finds all entities with active 1003 lookup errors and rebuilds their search index entries using the resolved canonical value. This step clears the stale facet values from Advanced Search.

Via API:

POST https://<environment>.reltio.com/reltio/api/<tenantId>/reindexUnresolvedRdmLookups
Authorization: Bearer {token}

No request body is required to reindex all affected entities. 

Via Console UI:

1. Open the Applications menu → Console
2. Select Tenant Management → select your MDM tenant
3. Navigate to Jobs → Create New Job
4. Select Reindex Unresolved RDM Lookups → Run Job
5. Monitor progress under the PENDING tab; confirm completion under COMPLETED

After completion, verify that the stale facet value no longer appears in Advanced Search.

Step 4 — Full Reindex (if stale entries persist)

If stale facet values remain after Step 3, run a full tenant reindex to ensure complete search index consistency.

POST https://<environment>.reltio.com/reltio/reindex?tenantId=<tenantId>&updateEntities=true&enableSeparateIndexing=true&distributed=true&taskPartsCount=<taskParts>

Note: Contact Reltio Support to confirm the correct taskPartsCount value before running a full reindex on Production or check your physical tenant for maxTaskCount

Verification

After completing the steps above, verify the fix in Advanced Search:

1. Open Advanced Search in the MDM Hub
2. Filter by the affected attribute (for example, Business Identifiers / Type = Equals)
3. Confirm the old canonical value no longer appears as a facet option
4. Confirm all previously affected records now appear under the new canonical value

To verify via API before and after reindex:

# Find all entities with unresolved RDM lookup errors
GET {TenantURL}/entities?filter=equals(rdmLookups.resolved,false)

# Find entities with lookup errors on a specific nested attribute
GET {TenantURL}/entities?filter=exists(rdmLookups.attributes.Identifiers.Type)

After a successful reindex, equals(rdmLookups.resolved,false) should return zero results for the affected attribute.

Prevention

To avoid this issue when renaming canonical values in RDM:

• Update all source system Value fields simultaneously with the canonical rename — Oracle EBS, Salesforce, Reltio source, and any other configured sources
• Do not leave any source codes in the Unmapped Values panel after a rename
• After saving, run Steps 2–3 above as standard post-rename hygiene even if no stale facet values are immediately visible
• When renaming in Production, schedule the RDM mapping updates and cache reset / reindex during a low-traffic window

Full Resolution Sequence — Quick Reference

Related Documentation

• Lookups and Canonical Values
• Resolve Mapping Errors API
• Reindex Unresolved RDM Lookups (Console UI)
• Reindexing Lookups in a Tenant
• RDM Task API