Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.4 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Configuration Guide

Configuration Guide

Back Next

Child Base Object Cascade Unmerge Behavior

Child Base Object Cascade Unmerge Behavior

The affect that the cascade unmerge process has on a child base object depends on whether the parent underwent the tree unmerge process or the linear unmerge process.
The following list shows the the configuration of the parent base object record and the child base object record before and after the cascade unmerge processes:
Merged parent base object record
The following graphic shows a parent base object record '1', which is the best version of the truth that consists of data from records '2' through '7':
The record hierarchy is a tree-like structure. The base object record is at the top, and related records split into two branches.
Merged child base object record
The following graphic shows the child base object record, '1', that has the same data structure as the parent base object record. The child base object record generally has a different structure from the parent base object record.
The record hierarchy is a tree-like structure. The base object record is at the top, and related records split into two branches. In this example, the child base object record has the same structure as the parent base object record.
Parent base object after a linear unmerge
The following graphic shows record '2' as a separate base object after it undergoes the linear unmerge process:
Unmerged records break away from original hierarchical structure. For a linear unmerge, the unmerged record breaks away into a base object record with no branches. The branches of the unmerged base object merge into the base object record at the top of the tree-like structure.
Child base object after a linear unmerge
When the parent base object record undergoes the linear unmerge process, the child base object record undergoes the same process. The following graphic shows that the affect of the parent base object record linear unmerge process has on the child base object record:
Unmerged records break away from original hierarchical structure. For a linear unmerge, the unmerged record breaks away into a base object record with no branches. The branches of the unmerged base object merge into the base object at the top of the tree-like structure. In this example, the structure of the child base object after the linear unmerge is the same as the parent base object.
Parent base object after a tree unmerge
The following graphic shows that record '2' is a separate base object that maintains its tree structure after it undergoes the tree unmerge process.
Unmerged records break away from original hierarchical structure. For a tree unmerge, the unmerged record breaks away from the original base object and retains the tree-like structure. The branches of the unmerged base object remain as branches of the unmerged base object.
Child base object after a tree unmerge
When the parent base object record undergoes the tree unmerge process, the unmerged tree in the child base object undergoes the linear unmerge process. The following graphic shows the affect that the parent base object record tree unmerge process has on the child base object record:
Unmerged records break away from original hierarchical structure. For a tree unmerge, the unmerged record and all branches of the unmerged record in the child base object break away into individual child base object records.
0 COMMENTS
We’d like to hear from you!