Sample Issue:
RDM values that are already mapped also exist in the unmapped section as below:
Solution:
The “CleanupInvalidUnmapped“ task should delete those unmapped value for which a mapping exist in RDM.
Cleanups Unmapped table in a primary storage.
Parameters
This task type doesn’t have parameters.
This task should delete those unmapped value for which a mapping exist.
Examples
Cleanup Unmapped table for a tenant
POST https://{{rdm-service}}/tasks/{{tenantId}}
Authorization: Bearer {{token}}
{
"type": "cleanupInvalidUnmapped"
}
To clean duplicate unmapped values
POST https://{{rdm-service}}/tasks/{{tenantId}}
Authorization: Bearer {{token}}
{
"type": "cleanupInvalidUnmapped",
"parameters": {
"checkAllMapping": "true"
}
}
Comments
Hi, what else we can pass in the parameters, and "checkAllMapping": "true" what does this mean?
To clean up unmapped value from the tenant use "type": "cleanupInvalidUnmapped"
To clean duplicate unmapped values you need to add the parameter: "checkAllMapping": "true"
This will run on all lookup right? what if we have to run for specific lookup type
As of now, this is only for all the lookups.
Please sign in to leave a comment.