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.3 HotFix 3
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction
  3. Configuring the Data Director Application
  4. Establishing a Root Node
  5. Defining the Business Entity Model
  6. Configuring Business Entity Properties
  7. Configuring Reference Entity Properties
  8. Transforming Business Entities and Views
  9. Managing Many-to-Many Relationships
  10. Configuring Search
  11. Configuring Workflow Tasks and Triggers
  12. Configuring Security and Data Filters for Business Entities
  13. Integrating Data as a Service
  14. Configuring External Calls
  15. Designing the Data Director User Interface
  16. Localizing Data Director
  17. Provisioning Tool Frequently Asked Questions

Provisioning Tool Guide

Provisioning Tool Guide

Back Next

Setting Strategies for Record Deletion and Record Checking

Setting Strategies for Record Deletion and Record Checking

By default, the MDM Hub always identifies existing records by the ROWID_OBJECT value and by the primary key and source system. However, in the many field of the business entity root element, you can set additional strategies to determine how the MDM Hub deletes and identifies child base object records.

Delete strategy

Determines the behavior when you delete a child record.
When you enable the
Delete strategy
 check box, select one of the following values:
DISASSOCIATE
Records remain active but the foreign key is set to null. Default is DISASSOCIATE.
SOFT_DELETE
Soft-deletes the record. The MDM Hub sets the HUB_STATE_IND to -1.
DELETE_PARENT
Deletes the record from the relationship table. The child record is not deleted.

Identifying strategy

Determines how the MDM Hub checks for an existing child record. When you add a child record to a business entity, the MDM Hub determines if the record is new or already exists.
When you enable the
Identifying strategy
 check box, configure the following attributes:
oneRow
Determines the behavior when a record exists.
The
oneRow
 attribute can have the following values:
ACCEPT
The MDM Hub does not create a child record. Default is ACCEPT.
CREATE
The MDM Hub creates a child record.
ERROR
The MDM Hub does not create a child record. An error occurs.
noRow
Determines the behavior when a record does not exist.
The
noRow
 attribute can have the following values:
CREATE
The MDM Hub creates a child record.
ERROR
The MDM Hub does not create a child record. An error occurs.
0 COMMENTS
We’d like to hear from you!