Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Sizing and Platform Requirements
  9. Application Components
  10. IDD Security Configuration
  11. Data Security
  12. Example Role-Based Security Configuration
  13. Data Masking
  14. Siperian BPM Workflow Engine
  15. Locale Codes
  16. Troubleshooting
  17. Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Many:Many Grandchild Relationships

Many:Many Grandchild Relationships

For many:many relationships, the grandchild record is related to a child object through a relationship table.
IDD supports two kinds of many:many relationships: If the child is a many:many, the foreign key can be either to the (see the data model examples below):
  • Child record
  • Relationships record.
The following table describes the types of many:many grandchild relationships:
Relationship
Description
Part Of
The grandchild record belongs to the primary object - no other subject area should reference this grandchild. When adding a grandchild, both the relationship and grandchild records are added. When editing a grandchild, if another subject area references it, a copy of the grandchild is created. The data referenced by the other child remains unchanged.
Reference
The grandchild is another subject area. When adding a grandchild, only a relationship record is added. The IDD application user must search for the subject area grandchild to be referenced. To edit the grandchild data, the subject area for that grandchild must be opened. This grandchild can be linked through a standard relationship Base Object or an HM relationship Base Object.
When configuring the match path for grandchildren in the Schema Manager of the Hub Console, ensure that
Check Missing Child
is disabled. IDD application do not function properly if
Check Missing Child
is enabled.

0 COMMENTS

We’d like to hear from you!