Table of Contents

Search

  1. Preface
  2. Introduction to Business Entity Services
  3. Enterprise Java Bean Business Entity Service Calls
  4. Representational State Transfer Business Entity Service Calls
  5. Simple Object Access Protocol Business Entity Service Calls
  6. Services for Cross-reference Records and BVT Calculations
  7. Supporting Corporate Linkage Service
  8. External Calls to Cleanse, Analyze, and Transform Data
  9. Appendix A: Using REST APIs to Add Records
  10. Appendix B: Using REST APIs to Upload Files
  11. Appendix C: Using REST APIs to Manage Reports

Remove Mismatched Source Data

Remove Mismatched Source Data

If a cross-reference record is incorrectly associated with a particular master record, a data steward can unmerge the cross-reference record. A new master record is created from the unmerged cross-reference record.
Only one cross-reference record can be unmerged in an unmerge call. If several cross-reference records need to be unmerged, make an unmerge call for each cross-reference record.
If a trigger is configured for an unmerge event, then an unmerge task is created. Otherwise, the cross-reference record is unmerged.
The URL and command to unmerge a record based on the system name and source key has the following format:
POST http://<host>:<port>/<context>/<database ID>/<business entity>/<row ID>?action=unmerge&systemName=<source system name> { name: "<object name>", key: {rowid: "<rowid value>", sourcekey: "<source key>", systemName: "<source system name>" } }
The URL and command to unmerge a record based on the cross-reference record ID has the following format:
POST http://<host>:<port>/<context>/<database ID>/<business entity>/<row ID>?action=unmerge&systemName=<source system name> { name: "<object name>", key: {rowid: "<rowid value>", rowidXref: "<row ID of xref>"} }

0 COMMENTS

We’d like to hear from you!