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. Appendix A: Sizing and Platform Requirements
  9. Appendix B: Application Components
  10. Appendix C: IDD Security Configuration
  11. Appendix D: Data Security
  12. Appendix E: Example Role-Based Security Configuration
  13. Appendix F: Data Masking
  14. Appendix G: Siperian BPM Workflow Engine
  15. Appendix H: Locale Codes
  16. Appendix I: Troubleshooting
  17. Appendix J: Glossary

Data Director Implementation Guide

Data Director Implementation Guide

One:Many Child Relationships

One:Many Child Relationships

For one:many relationships, the child record has a direct foreign key to the primary object. IDD supports two kinds of one:many relationships.
The following table describes the types of one:many child relationships:
Relationship
Description
One:Many
The list of child records will be displayed in a tab below the primary data.
Logical One:One
The expectation is that there should be only one child record for each primary object. The data is shown in the form with the primary object. If there is more than one child (due, for example, to two primary object records being merged), the IDD application provides a means to resolve this.

0 COMMENTS

We’d like to hear from you!