FAQ on derived relations

This topic contains answers to frequently asked questions (FAQ) on derived relations, including solutions to common issues.

• Can I migrate derived relation types from one environment to another?

  Yes, you can migrate derived relation types from one environment to another.

• Do I need view permissions for every intermediate asset in a relation path to see a derived relation?

  No. View permissions are applied only to the query results. Collibra first calculates the end-to-end connection based on the derived relation type definition. Once the calculation is complete, it simply hides any final target assets from the results if you don't have permission to view them. Lacking view permissions on the intermediate assets between the head and the tail doesn't influence the calculation.

• Can I use an asset type group as the head or tail in a derived relation type?

  No, you can't use an asset type group 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.

• Why is the derived relation section not visible on the asset page?

  Ensure that your derived relation type is assigned to the asset type. If the asset type has an out-of-the-box or custom asset layout, ensure that the derived relation type is also added to the layout.
  

• Why is the derived relation section on an asset page empty?

  If the derived relation section is visible on an asset page but empty, it could be due to one of the following reasons:

  • There are simply no assets at the other end of the relation path.
  • Your operating model has been updated, rendering the asset type incompatible with the derived relation type.
  • The asset you are viewing doesn't meet the filter condition defined in the derived relation type.
    
    Example Consider the following derived relation type: "Database (status = Accepted) contains / is part of Column (status = Candidate)". If you are on the asset page of a database in Rejected status, the derived relation section returns no results because only databases in Accepted status are included in the head filter.
  • The assets at the other end of the relation path don't meet the filter condition defined in the derived relation type.
    
    Example Consider the same derived relation type. If you are on the asset page of a database in Accepted status, but the database only contains columns in New status, the derived relation section returns no results because only columns in Candidate status are included in the tail filter.

• Can I delete an asset type that is used as the head or tail of a derived relation type?

  No, you can't delete an asset type that is used as the head or tail of a derived relation type.

• What do I need to do before deactivating the "Derived relation support" setting?

  Derived relation types remain visible in asset type assignments even after the Derived relation support setting in Collibra Console is deactivated. This is because characteristic types within an assignment are ordered and identified by numbers. While this behavior preserves data consistency, it can cause unintended side effects in certain integrations and workflows. Therefore, before deactivating the Derived relation support setting, remove any derived relation types from asset type assignments.