A complex relation is a characteristic that shows how two or more assets are related to one another. It can have attributes of its own, for example, Description and Priority. Technically, a complex relation is an entity that can't exist on its own. It exists only through its links to other assets. The complex relation type defines which relations and attributes a complex relation can have.
The following table contains out-of-the-box complex relation types.
Tip In the latest UI, in the Complex relation types table in the Operating Model settings:
- You can find which asset types use a specific item by selecting the row containing the item and then clicking Used In.
- The System Managed column indicates whether the item is provided out of the box (OOTB) and managed by Collibra. All system-managed items are OOTB, but not all OOTB items are system-managed.
means that the item is OOTB. 
means that the item is either custom-created or an editable OOTB item.
| Name | Description | Relation types | Attribute types | Assigned asset types |
|---|---|---|---|---|
| Code Mapping | Complex mapping between two or more code values | Source - Code Value (1:-) |
|
|
| Target - Code Value (1:-) | ||||
| Crosswalk - Crosswalk (1: 1) | ||||
| Data Usage | Data Usage | Uses - Data Asset (1:-) |
|
|
| Used in - Business Asset (1:-) | ||||
| Governed by - Rule (1:-) | ||||
| Fact Type | Head - Asset (1: 1) |
|
|
|
|
Tail - Asset (1: 1) |
||||
| Field Mapping | Complex mapping between two or more data fields | Source - Data Element (1:-) |
|
|
| Target - Data Element (1:-) | ||||
| Mapping specification - Mapping Specification (1: 1) | ||||
| Foreign Key Mapping | Complex mapping between two columns representing a primary key and a foreign key | Constrains - Column (1: 1) |
|
|
| References - Column (1: 1) | ||||
| Is part of - Foreign Key (1: 1) |