Usage guidelines for derived relations

Usage guideline	Description
Maximum explicit relation types per derived relation type	A derived relation type cannot include more than 50 explicit relation types. If your derived relation type includes other derived relation types, this limit applies only after all the nested derived relation types in a relation path are resolved. Nested derived relation types are resolved by replacing each derived relation type with its own path, repeating this recursively until only explicit relation types remain. Only after all the nested derived relation types are resolved is the total number of explicit relation types counted toward the limit. This total must not exceed 50. Additionally, if you use repeated relations, the maximum number of repetitions you set counts toward this calculation. For example, if you set a relation type to repeat a maximum of 5 times, Collibra counts that as 5 explicit relation types against your 50-explicit relation type limit.
Maximum explicit relation types in a straight relation path	A relation path from the head to the tail in a derived relation type cannot contain more than 10 explicit relation types. This limit is calculated based on explicit relation types, after each included derived relation type has been replaced by its relation paths. Additionally, if you use repeated relations, the maximum number of repetitions you set counts toward this calculation. For example, if you set a relation type to repeat a maximum of 4 times, Collibra counts that as 4 explicit relation types against your 10-explicit relation type limit for that specific path.
Maximum filters in a derived relation type	A derived relation type cannot contain more than 100 total filters across all its relation paths.
Maximum nested expressions in a filter formula	A filter formula cannot contain more than 5 nested expressions. For example, formulas with a nesting depth of 4, such as `((((A))))`, or a depth of 2, such as `((A OR B) AND (C OR D))`, are valid. However, a formula such as `((((((A))))))` is invalid because it has a nesting depth of 6, which exceeds the limit.
Timeout threshold	The database query to find the assets at the end of a derived relation is canceled if it takes more than 10 seconds to complete.
Loop prevention	You cannot generate a loop inside your relation path (A → B → A). That is, you can't reference a node that you already traversed while following a relation path, including the current node. This also applies when you include a derived relation type within another derived relation type. In particular, a relation path can't include itself.
Out-of-the-box restrictions	You cannot remove a relation type from the relation path of an out-of-the-box derived relation type, unless you added that relation type.
Graph node labels and codes	On the Graph tab in the derived relation type editor, the label and the code shown for a node may not always match.
Sort order logic	On the Relation types page in the Operating Model settings, in the Kind column, ascending order always lists derived relation types first, and descending order lists explicit relation types first—regardless of your language settings.
Asset type groups	An asset type group cannot be used as the head or tail in a derived relation type. If you need to use a relation that relies on an asset type group at the end of a relation path, select a common ancestor asset type instead, for example, Asset, and then use an asset type filter on the head or tail node.
Maximum derived related assets shown on an asset page	A maximum of 50 derived related assets are shown per derived relation type section on an asset page.
Filtering and search in the derived relation view	Filtering and search are not available in the derived relation view on asset pages.
HTML-formatted values in derived relation type filters	The Equals operator for an attribute in a derived relation type filter matches only plain text values; it doesn't match HTML-formatted values.

Maximum explicit relation types per derived relation type

A derived relation type cannot include more than 50 explicit relation types. If your derived relation type includes other derived relation types, this limit applies only after all the nested derived relation types in a relation path are resolved. Nested derived relation types are resolved by replacing each derived relation type with its own path, repeating this recursively until only explicit relation types remain. Only after all the nested derived relation types are resolved is the total number of explicit relation types counted toward the limit. This total must not exceed 50.

Additionally, if you use repeated relations, the maximum number of repetitions you set counts toward this calculation. For example, if you set a relation type to repeat a maximum of 5 times, Collibra counts that as 5 explicit relation types against your 50-explicit relation type limit.

Maximum explicit relation types in a straight relation path

A relation path from the head to the tail in a derived relation type cannot contain more than 10 explicit relation types. This limit is calculated based on explicit relation types, after each included derived relation type has been replaced by its relation paths.

Additionally, if you use repeated relations, the maximum number of repetitions you set counts toward this calculation. For example, if you set a relation type to repeat a maximum of 4 times, Collibra counts that as 4 explicit relation types against your 10-explicit relation type limit for that specific path.

Maximum filters in a derived relation type

A derived relation type cannot contain more than 100 total filters across all its relation paths.

Maximum nested expressions in a filter formula

A filter formula cannot contain more than 5 nested expressions.

For example, formulas with a nesting depth of 4, such as ((((A)))), or a depth of 2, such as ((A OR B) AND (C OR D)), are valid. However, a formula such as ((((((A)))))) is invalid because it has a nesting depth of 6, which exceeds the limit.

Timeout threshold

The database query to find the assets at the end of a derived relation is canceled if it takes more than 10 seconds to complete.

Loop prevention

You cannot generate a loop inside your relation path (A → B → A). That is, you can't reference a node that you already traversed while following a relation path, including the current node. This also applies when you include a derived relation type within another derived relation type. In particular, a relation path can't include itself.

Out-of-the-box restrictions

You cannot remove a relation type from the relation path of an out-of-the-box derived relation type, unless you added that relation type.

Graph node labels and codes

On the Graph tab in the derived relation type editor, the label and the code shown for a node may not always match.

Sort order logic

On the Relation types page in the Operating Model settings, in the Kind column, ascending order always lists derived relation types first, and descending order lists explicit relation types first—regardless of your language settings.

Asset type groups

An asset type group cannot be used as the head or tail in a derived relation type. If you need to use a relation that relies on an asset type group at the end of a relation path, select a common ancestor asset type instead, for example, Asset, and then use an asset type filter on the head or tail node.

Maximum derived related assets shown on an asset page

A maximum of 50 derived related assets are shown per derived relation type section on an asset page.

Filtering and search in the derived relation view

Filtering and search are not available in the derived relation view on asset pages.

HTML-formatted values in derived relation type filters

The Equals operator for an attribute in a derived relation type filter matches only plain text values; it doesn't match HTML-formatted values.

Image of DRT filter with unicode characters