Cardinality in table relations recap in Microsoft Dynamics 365 Finance and Operations apps

ZeroOne

0 to 1

ExactlyOne

1 to 1

ZeroMore

0 to n

OneMore

1 to n

RelatedCardinality

ZeroOne

0 or 1

ExactlyOne

1 or 1

NotSpecified

Often the default value for the RelationshipType property.

Specialization

(table inheritance)

Applies only to table inheritance, to relationships between base and derived tables.

Link

(EDT migration in AX 2012)

Is a non-relational relationship. Link requires that the Validate property be set to No.

This type of relationship supports navigation between forms that list many records from a table and forms that provide detail fields for one record from the table.

Composition

(Ownership, like parent and child)

Is a stronger type of Aggregation. A table must not have more than one Composition relation. For example, a building is composed of rooms, and a given room cannot exist in more than one building.

Aggregation

Is appropriate when the child table is considered to be subordinate to the entity of the parent table.

Association (linked like guardian and child)

The concept of a standard foreign key.