AcceptUnmatchedRecordsAsUnique changes the state of records that have no match candidates from Unmerged to Consolidated (unique). Once a record is in the Consolidated state, it will no longer appear in the list of records that needs to be reviewed and it will not be merged by the merge batch process. These records can still be merged manually in the Console or by using the Merge API.
The request specifies the base object table or a package on that table. It also supplies a boolean value indicating whether or not to change only those records assigned to the user.
The response contains the number of records accepted as unique.
You can configure AcceptUnmatchedRecordsAsUnique requests only for “no system” when using the Hub Console Audit Manager to audit requests made by external applications. Once auditing for a particular SIF API request is enabled, Informatica MDM Hub captures each SIF request invocation and response in the audit log. For more information, see the
Multidomain MDM Configuration Guide
.
Use Case
This is the common scenario for using the AcceptUnmatchedRecordsAsUnique request:
Set unmatched records as unique
— You can use the AcceptUnmatchedRecordsAsUnique request in an application with a custom UI for the data stewards. In the screen that manages the status of records, you might create a button that uses this request to accept all the unmatched records as unique.