Preface
Part 1: Introduction
Part 2: Configuring Hub Console Tools
- Configuring Access to Hub Console Tools
- Implementing Custom Buttons in Hub Console Tools
Part 3: Building the Data Model
Part 4: Configuring the Data Flow
Part 5: Executing Informatica MDM Hub Processes
- Using Batch Jobs
- User Exits
Part 6: Configuring Application Access
Appendix A: MDM Hub Properties
Appendix B: Viewing Configuration Details
Appendix C: Row-level Locking
Appendix D: MDM Hub Logging
Appendix E: Table Partitioning
- Support for Table Partitioning
Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
Appendix G: Informatica Platform Staging
Appendix H: Informatica Platform Mapping Examples
- Informatica Platform Mapping Examples Overview
- Generate Primary Keys Example
Appendix I: Glossary
- Glossary of Terms

Configuration Guide

10.4

Back Next

Record States and Base Object Record Value Survivorship

After a merge, put, or load process, a base object record might have multiple cross-reference records with different record states. In this case, the values in the base object record reflect only the values from the active cross-reference records.

In general, when resolving multiple records with different states, the

MDM Hub

processes apply the following rules:

Values in active records prevail over values in pending or deleted records.

Values in pending records prevail over values in deleted records.

For a match and merge operation, the source and target of the records to merge determines the surviving Rowid, not the record state.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Record States and Base Object Record Value Survivorship

Record States and Base Object Record Value Survivorship