How can I fix a Unmapped Lookup Value

Problem:

I see an error message "Lookup resolving error: 1003: RDM canonical value mapping not found for value"

I can see the unmapped error in the RDM console.

How can I fix this error?

Solution:

  • If the feature for track transcode errors is turned on, every time when linked MDM tenant has a transcode problem, RDM creates an unmapped value. 
  • If you have unmapped values, you can fix them by drag&drop unmapped on the mapping tab. After that, when you save changes, UI creates new mapping and removes the unnecessary unmapped. This is a single way to “clear“a list of unmapped values.
  • If you have an unmapped value and have the same lookup mapping, you could use an RDM API request to remove redundant unmapped values (as defined below)
  • You can execute the following task to remove a specific RDM lookup
POST https://rdm.reltio.com/tasks/<rdmTenant>
{
"type": "deleteUnmapped",
"parameters": {
"type": "rdm/lookupTypes/LOBSurvivorshipOrder"
  }
}
  • You will see that the task is completed as expected
 {
"id": "9849f112-f45b-4fef-8f74-2b5ffe283e05",
"type": "deleteUnmapped",
"tenantId": "<tenantId>",
"createdBy": "gloria.faley@reltio.com",
"createdTime": 1639702088450,
"status": "FINISHED",
"parameters": {
"type": "rdm/lookupTypes/LOBSurvivorshipOrder"
        },
"result": {
"Value processed": 7, <<- number of lookup that were fixed in the task.
"Errors": 0,
"Average per second": 8.526187576126675,
"Execution time": 821
        }
    },
  • It is also possible to execute the following API to remove all redundant unmapped values.
POST https://rdm.reltio.com/tasks/jSoM3LsHSJPudCJ
{
"type": "deleteUnmapped"
}
  •  After fixing unmapped errors, you should perform the following task to execute reindex entities to resolve unresolved RDM lookups in MDM.
POST https://<environment>.reltio.com/reltio/api/<MDMTenantID>/reindexUnresolvedRdmLookups
  • Please also execute a reindex of the RDM (either full or the specific lookup type)
POST https://{{rdm-service}}/tasks/{{tenantId}}
Authorization: Bearer {{token}}
{
  "type": "reindex"
}
POST https://{{rdm-service}}/tasks/{{tenantId}}
Authorization: Bearer {{token}}
{
  "type": "reindex",
  "parameters": {
    "type": "rdm/lookupTypes/Country"
  }
}
  • If you are making a bulk change in the L3 (data model) to attributes that are using RDM lookup value, please perform a full MDM reindex (where the task builds a new index)
POST {ApplicationURL}/reindex?tenantId={tenantId}?enableSeparateIndexing=true
  • If you still have what appears to be a redundant unmapped value in RDM, please check for any special character.  

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.