Resolving RDM Lookup Errors from MDM

You may encounter mapping errors due to unresolved lookups in MDM.

After a data load to MDM, you may encounter mapping errors due to unresolved lookups. For example, the transcoded value from RDM for the Gender attribute is Male. If an entity with the value M is loaded, the entity is loaded with an invalid value. This results in a mapping error that must be resolved in RDM.

When an RDM lookup error is reported in MDM, the error is sent to RDM and it appears as an unmapped value in the unmapped drawer under the corresponding source. If the same lookup error (lookup type, value, and source) combination is reported for multiple entities, only one error appears in the unmapped drawer in RDM. Alternatively, if one entity reports multiple lookup errors, then all errors appear as unmapped values in the unmapped drawer. You can map the unmapped values from the unmapped drawer and resolve the lookup errors. After the lookup errors are mapped and resolved:

If the RDM cache is enabled for the MDM tenant, then the updated mappings are applied when the RDM cache is updated on the MDM tenant.
If the RDM cache is disabled for the MDM tenant, then the updated mappings are applied immediately.

The information about lookup errors is sent to RDM based on the configuration of the following parameters:

publishRDMErrors - in the MDM physical tenant configuration, the default value is false. If set to true, MDM tenants can send lookup errors to the RDM tenant.
trackTranscodeErrors – in the RDM tenant configuration, the default value is false. If set to true, then lookup errors sent from MDM appear in the unmapped drawer in RDM.

The RDM configuration parameter overrides the MDM tenant configuration parameter. If publishRDMErrors is set to true and trackTranscodeErrors is set to false, then no lookup errors are sent to the unmapped drawer in RDM. If publishRDMErrors is set to false and trackTranscodeErrors is set to true, then also no lookup errors are sent to the unmapped drawer in RDM. Therefore, for lookup errors to be sent to RDM, both parameters must be set to true.

These parameters also ensure that if the data in the RDM tenant is corrupted, MDM tenants can stop sending lookup errors to the RDM tenant. This is useful if multiple MDM tenants are connected to one RDM tenant.

Note: To set the values of these parameters, contact Reltio Customer Support.

After the lookup errors appear in the unmapped drawer, you can map the unmapped values to resolve the errors. For more information, see Mapping Unmapped Values.

During runtime, you cannot use an unmapped page for checking transcode errors. The unmapped values pane shows unmapped values which were uploaded to the RDM tenant.

Every time when the linked MDM tenant has a transcode issue, RDM creates an unmapped value.

Note: On a linked MDM tenant, the hierarchy transcode fails and the unmapped value is not created.

While you resolve errors in lookup mapping, you must update the list of unmapped values manually. You can update the list of unmapped values manually in the following ways:

Resolve transcode issues by dragging and dropping the unmapped value on the mapping page. In this scenario, when lookup mapping is created or updated, unmapped values will be removed.
Remove the redundant unmapped values by the API request.

For more information, see Mapping Unmapped Values.

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

© 2024 The RELTIO® mark is a registered trademark of Reltio, Inc. in the United States and other countries; DataDriven and Reltio Data Cloud are trademarks of Reltio, Inc. Other names or marks are trademarks of their respective owners.

Terms, Privacy Policy, and

Unify and manage your data

Resolving RDM Lookup Errors from MDM

Footer