Cardinality In a Conceptual Object
Conceptual objects can be configured to use cardinality rules. The cardinality of a conceptual object indicates the minimum and maximum number of child records each parent record in that object must have.
Cardinality | Description |
Minimum cardinality | Minimum number of child values that can belong to a particular parent node. |
Maximum cardinality | Maximum number of child values that can belong to a particular parent node. |
If a business rule requires that every parent record created must have at least one child record, the following cardinality rule is used:
Level | Minimum Cardinality | Maximum Cardinality |
Parent | Not applicable | Not applicable |
Child1 (parent of child 2) | 1 | |
Child2 | 0 | |
Note: The minimum cardinality rule is only applicable when inserting a record in a root node. Updates are not impacted. The maximum number of child nodes that can be created at the time of creation of the root node is 9.
If a business rule requires that every parent record created must have at least one child record, and each of these child records should have at least two child records, the following cardinality rule is used:
Level | Minimum Cardinality | Maximum Cardinality |
Parent | Not applicable | Not applicable |
Child1 (parent of child 2) | 1 | |
Child2 | 2 | |