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. Configuring Hierarchy and Network Relationships
  10. Creating Match Rule Sets
  11. Configuring Search
  12. Configuring Tasks
  13. Configuring Security and Data Filters for Business Entities
  14. Configuring the Content Security Policy
  15. Integrating Data as a Service
  16. Configuring External Calls
  17. Designing the Data Director User Interface
  18. Localizing Data Director
  19. Appendix A: Provisioning Tool Frequently Asked Questions

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, 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:
Values
Description
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 options:
Option
Description
One Row
Determines the behavior when a record exists. Select one of 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.
No Row
Determines the behavior when a record does not exist. Select one of the following values:
  • Create. The MDM Hub creates a child record
  • Error. The MDM Hub does not create a child record. An error occurs.
Unique Field
Field by which the MDM Hub identifies whether a child record is unique.
Label Format
Specifies the format of labels shown in the user interface. A label can be configured to include a subset of fields from the business entity record. For example, the Person: {lastname}, {firstname} will be shown as follows in the user interface: Person: John, Smith.

0 COMMENTS

We’d like to hear from you!