Once you've reloaded the correct unmapped lookup values to the RDM tenant, follow these four key steps to resolve transcode errors in your MDM tenant fully:
Delete obsolete unmapped entries from RDM (cleanup)
Use this to clean up no-longer-relevant unmapped references:
Payload:
Reindex the RDM tenant
This updates the lookup index so that values are recognized during entity ingestion and lookup resolution.
POST https://<rdm_env>.reltio.com/reltio/api/<rdmTenant>/tasks?type=reindex
Reindex the unresolved RDM Lookups in the MDM tenant
This will reprocess all entities, including your specific one, to apply the newly mapped lookup values and clear the transcode errors.
POST https://<environment>.reltio.com/reltio/api/<MDMTenantID>/reindexUnresolvedRdmLookups
Run a full reindex on the MDM tenant.
If we change the code (not the value) in RDM, we need to perform a reindex. It is recommended to use a separate reindexing option, as this is the only way to overwrite data in Elasticsearch (ES) if the MDM portion of the data has not changed. While reindexing in a separate index isn’t always an ideal choice, in the case of changing the lookup code, it is the best option.
POST https://<environment>.reltio.com/reltio/reindex
?tenantId={tenantId}&enableSeparateIndexing=true&updateEntities=true
&forceIgnoreInStreaming=true&taskPartsCount=4&distributed=true
Verify if there are any additional unresolved lookups in the MDM.
POST https://<environment>.reltio.com/reltio/API/api/<tenantId>/entities/_total
Payload
{
"filter": "equals(rdmLookups.resolved,'false')",
"options": "searchByOv,ovOnly",
"activeness": "active"
}
Reset the cache on the RDM Tenant
-
This call clears the RDM lookup cache, used explicitly by MDM.
-
It does not replace
reindex
tasks, which are still needed to reprocess entity data. -
Use this after RDM reindexing and before MDM reindexing to prevent stale lookup references during processing.
POST: https://<environment>.reltio.com
/reltio/resetRDMCache
Comments
Please sign in to leave a comment.