CanUnmergeRecords determines whether or not specified records can be unmerged from the consolidated base object. The request contains a package and a key identifying the XREF to unmerge. The response contains a boolean value that is true if the records can be unmerged, false if they cannot.
Cross reference records can be added to a base object record either by consolidating two base object records or by adding them directly using the ROWID_OBJECT of a base object record. If a cross reference is added using the ROWID_OBJECT and no PKEY_SOURCE_OBJECT, and there is not already a cross reference for that base object record for the specified system, a new cross reference record is added that is considered an “edit” cross reference.
An unmerge is not allowed if the specified cross reference is not an edit cross reference and all the other cross references for that base object are edit cross references. If there are at least two cross references that are not edit cross references, the cross reference can be unmerged.
You can configure CanUnmergeRecords requests according to a specific 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 CanUnmergeRecords request:
Determining whether a given record can be unmerged
—You can use the CanUnmergeRecords request in an application with a custom UI for the data stewards to determine whether two records can be unmerged before attempting to do so.