Import asset types and relationships - Precisely Data Integrity Suite

Data Integrity Suite

Product

Spatial_Analytics

dis_mcp

Data_Integration

Data_Enrichment

Data_Governance

Precisely_Data_Integrity_Suite

geo_addressing_1

platform_spatial_analytics

Data_Observability

Data_Quality

dis_core_foundation

Services

Spatial Analytics

Precisely MCP

Data Integration

Data Enrichment

Data Governance

Geo Addressing

Data Observability

Data Quality

Core Foundation

ft:title

Data Integrity Suite

ft:locale

en-US

PublicationType

pt_product_guide

copyrightfirst

2000

copyrightlast

2026

Use the Import feature to upload and manage business and technical assets and their relationships in Data Integrity Suite. For larger volumes, compile multiple records in a spreadsheet and upload them all at once.

Key capabilities include:

Spreadsheet template: Download a predefined spreadsheet template to input asset or relationship data, and then upload it.
Import processing: The system validates and processes CSV or XLSX files for bulk addition, update, or deletion of assets and relationships. Uploaded records are persisted in the catalog and made available in the UI, maintaining data integrity and operational efficiency.
Monitoring and error reporting: Track the progress of your uploads in real-time and receive detailed error reports for any issues encountered.
Error handling: If any record contains invalid information, that record is flagged for review. The import continues for valid records so that correct data is still imported successfully.

Note: Asset updates can use Asset Xref or configured key fields. When key-field matching is enabled, the import process automatically uses the existing key-field configuration for the asset type. No additional import pages, settings, or APIs are required.

This enhancement to the previous xref-only update behavior enables asset import validation based on key-field matching. If an import row contains both an xref and key fields, the process updates the matched asset and can update its key-field values. If a row does not contain an xref, the import looks for an existing asset with the same key-field values before creating a new asset.

Key fields can include list and reference-list field types that identify an existing catalog asset and support import validation.

For hierarchical assets, the parent asset is part of the unique identification. As a result, child assets with identical key-field values under different parent assets are treated as separate assets.

Key-field matching applies only to asset imports. Relationship imports continue to use the existing relationship import behavior.

Note: When creating a new relationship, if one side of the relationship does not exist, the system automatically generates a placeholder asset. After the placeholder is created, you must convert it to a real asset by providing the necessary information and attributes, so it is fully integrated into the system.

Go to Configuration > Import.
Select Import to start a new import.
For Import Type, select the type of asset or relationship you want to import: Technical Assets, Business Assets, Users, Models, Policies, Reference Lists, or Relationships.
Select the Import Action.
- For assets, the default import action lets you add or update assets.
- For relationships, select the add or update import action, or select Delete to remove relationships.
Note: Deleting relationships does not affect the associated asset fields. Asset field integrity is maintained regardless of relationship deletions.
From the dropdown menu, select the Type of asset or relationship you want to import. You can also include a Description.
Note: The Columns page in the side panel lists all required and optional fields for the selected import type. These fields appear as column headers in the spreadsheet template.
You can turn on the Trigger workflows toggle to initiate workflows associated with this asset type.
Note: During the import process, the system displays available workflows in the Triggered Workflows page in the side panel. If no workflows are available, this is indicated in the side panel, and the toggle to trigger workflows is disabled. Select the workflow links to view detailed information in a secondary panel, which can be closed to continue the import.
Select Download Spreadsheet Template. The template includes the required fields and columns based on the type you select. Mandatory columns for required fields are shown in bold.
Note: For relationship imports, the template includes the following columns:
- Subject Id: Source asset (provide either the unique ID or xref)
- Object Id: Target asset (provide either the unique ID or xref)
- Optional relationship properties as additional columns
To ensure accuracy and avoid errors, use either the unique ID or xref for both source and target assets.
Validate the file by ensuring that all required fields are filled out and that the data types match the expected formats.
Warning: Required fields must be provided when adding new assets. Each imported file is limited to a maximum size of 500 Megabytes. Uploaded files are retained for 90 days.
Upload the file by browsing and selecting a file from your computer, or by dragging and dropping it.
Tip: Ensure your file is in XLSX, XLS, or CSV format.
After uploading the file, import validation checks the following details:
- File format and required fields: Confirms that the uploaded file meets the required format and contains all required fields.
- Key fields: When key-field matching is enabled, checks that asset rows include the key-field values required to identify the asset, resolves key-field values to existing catalog assets, and performs an UPSERT operation. The import also checks that rows within the same import are not ambiguous duplicates and rejects rows that contain errors.
- Asset existence: Checks whether the assets referenced in the file exist. For hierarchical assets, placeholder assets are created when the referenced assets do not exist.
If validation fails due to errors such as invalid data or predicates, an error message is displayed that highlights the problematic records.
Select View errors or check the error messages for each row in the Errors page in the side panel. Errors can include missing key fields, duplicate key field combinations, conflicting asset matches, or lookup values that do not match existing catalog assets.
You can also re-upload only the rows that failed validation after making the necessary corrections.
After the import is configured, select Import to start the process. After a successful import, the system displays a confirmation message.

Track the progress of your import through status indicators: In Progress, Completed, Partial, and Failed.
Import child assets: When importing child assets, you must establish a parent-child relationship. The spreadsheet template includes a parent xref column. Provide the Asset Xref of the parent asset, which you can find on the asset Details page or side panel of the parent asset.
Update existing relationships: For existing relationships, the system updates them with the information you provide in the spreadsheet template.

Update existing assets using import

Bulk asset updates help maintain data accuracy and consistency across your system. The import process uses the xref or other unique identifiers in your spreadsheet to match records with existing assets. When a match is found, the asset's fields are updated based on the data and operations specified in the import file. Only columns included in your spreadsheet are affected; other fields remain unchanged.

The default add or update import action lets you modify existing assets, including their tags and relationships, without separate processes.
Validation and error handling: The system validates updates for required fields, data types, and field constraints (such as cardinality for relationship fields). If an update fails validation, the record is included in the error file with a descriptive message.
Reviewing update results: After the import, download the error and success files to review which assets were updated and which encountered issues. The error file provides details for each failed record, while the success file lists all successfully updated assets.

For more information on structuring the import spreadsheet, see Understand import spreadsheet template.

Update tags and relationships: Include the following operations and examples in your import spreadsheet, and prepare your data with the correct syntax for each action. The syntax determines how the system updates the tags and relationships.

Update tags

Action	Syntax	Description	Example	Result
Append (default)	None	Adds new tags to existing ones	`tag3`	Existing tags + `tag3`
Replace	`[replace]:tag4;tag5`	Overwrites all existing tags	`[replace]:tag4;tag5`	`tag4`, `tag5`
Remove specific	`[remove]:tag1;tag2`	Deletes specified tags	`[remove]:tag1;tag2`	Removes `tag1`, `tag2`
Remove all	`[remove]`	Clears all tags	`[remove]`	No tags (all cleared)

Update relationships

Action	Syntax	Description	Example	Result
Append (default)	None	Adds new relationships to existing ones	`object1;object2`	Existing relationships + new ones
Replace	`[replace]object1;object2`	Replaces all existing relationships	`[replace]object1;object2`	All previous relationships replaced
Remove specific	`[remove]object1`	Deletes specific relationship(s)	`[remove]object1`	Removes the specified relationship(s)
Remove all	`[remove]`	Clears all relationships	`[remove]`	No relationships (all cleared)

Note: Do not include any extra characters, spaces, or line breaks within the field.

Update other fields
- Because append is the default behavior for all fields, providing a new value updates the existing value by appending the data. For other fields (such as text or multi-select lists), provide a new value to update, or leave it empty to keep the current value unchanged.
- To remove a value from any field, use [remove].
- For multi-select list fields, [remove] clears all selected values.