Overview
Version 2 of the import wizard adds a series of improvements that might require you to adapt your input file.
Interface improvements
- The import wizard shifted the focus from Collibra characteristics to the fields of your file. Your fields are on the left side and allow mapping to the corresponding characteristics in Collibra on the right side. For an export-import round trip your fields are automatically mapped and you no longer need to select a specific view.
- A separate section displays all unmapped fields. It clearly indicates the fields which could not be automatically mapped. Once you map a field, it moves to the mapped section.
- The Configure Import dialog box has a new structure and more detailed information about your import options.
- To avoid unintentional changes, the import wizard explains the implications of deleting existing assets from the domain that are not in your import file before proceeding with the import.
- To help you troubleshoot, you can see a detailed table with the errors that happened during your import or test import.
Relations auto-mapping
To improve the automatic mapping for ambiguous relations, which correspond to multiple relations in Collibra, version 2 of the import wizard uses the source element of a relation type in the relation column headers. The header format changes from role [Target asset type] to [Source asset type] role [Target asset type], for example [Business Asset] has acronym [Acronym].
Note You can still use existing import templates, but to take advantage of a more accurate mapping, export the latest format with updated relation column headers.
Asset responsibilities
You can now import asset responsibilities. Because this action has performance implications, it is not enabled by default. You can toggle this feature via the Asset responsibilities support Collibra Console setting.
Starting workflows after import
You can decide whether to start workflows after a successful import by configuring the Enable workflows during import Collibra Console setting. This allows you to start workflows that are configured to run after a certain event, such as adding an asset to a domain, when that event is the result of an import operation.
Important Enabling workflows during import can have a significant impact on performance, based on the import volume. This configuration option is disabled by default.
Note Workflows do not start when using the Import REST API v2.
Handling of missing or unmapped data
To avoid creating undesired results, version 2 of the import wizard avoids making some assumptions for mandatory fields when the import file does not contain such values or you don't map the values during the import process. You should always provide an map values for domains, communities, and asset types to ensure the accuracy of the imported data. However, there are some scenarios where the import wizard can accurately determine how to handle missing or unmapped data.
Communities, domains, and domain types
You should always provide and map values for communities, domains, and domain types even if the import wizard can determine those values.
When you provide and map the asset ID, the import wizard treats the import as an update and does not assume any defaults. It takes the data you have provided and mapped in the import file and updates the assets accordingly.
When you start the import from a community, product, or global view page, and you don't map the asset ID you must provide and map the domain.
Starting with Collibra version 2023.05, when you start the import from a domain and you don't map the asset ID and the domain, the domain defaults to the current domain and any mapped domain types or communities are ignored.
When you start the import from a domain and you don't map the asset ID but you map the domain, the domain does not default to the current domain and any other mapped value is respected.
Asset types
Starting with Collibra version 2023.08, when you create new assets without providing the asset type, the import wizard defaults the asset type to Business Asset or a calculated value based on any provided relations.
| Scenario | Result |
|---|---|
| You don't map an asset ID and there are no relations. | The asset type defaults to Business Asset. |
| You don't map an asset ID and there is one relation. | The asset types for both the source and the target of the relation are determined by the asset types of that relation, for example [Business Asset] has acronym [Acronym]. |
| You don't map an asset ID and there are multiple relations with the same source asset type. |
The asset types for both the source and the target of the relation are determined by the asset types of those relations, for example [Business Asset] has acronym [Acronym] and [Business Asset] utilizes [Technology Asset]. Note Other assets without a relation are also imported with the same asset type as the source asset type. |
| You don't map an asset ID and there are multiple relations with the different source asset types. |
The asset type for the source of the relation is not defaulted. The asset type for the target is determined by the target asset types of the relations. Important Because in this scenario the asset type is missing, the import does not complete successfully. Note The asset type of other assets without a relation is also not defaulted. |
| You map an asset ID and there are relations. | The asset type for the target of the relation is determined by the target asset types of the relations. |
Starting with Collibra version 2023.08, when you import complex relations, the import wizard allows you to map the asset type. This means you can import complex relations also between new assets. Additionally, the import wizard can determine the asset type of the related assets based on the asset types of the complex relation.
Missing or partial data
When you explicitly map the community, domain, domain type or asset type for the primary or related assets, all the values are read from the input file. If the mapped columns contain missing data, for example some rows have data and some are empty, the empty values are not automatically defaulted. The exact values from the file, whether they are provided or empty, are used during import. This may result in an import error when values are missing.
Whitespace characters
Except for attributes, version 2 of the import wizard preserves any leading or trailing whitespace characters that your input file might contain.
Tip Ensure your input file does not contain any unwanted whitespace characters.