Import asset type configuration - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
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

Import an asset type configuration bundle into a target workspace after reviewing dependencies and resolving conflicts.

You must have permission to create asset types in the target workspace. The import file must be a configuration bundle created by the asset type configuration export flow.
Preview: This feature is currently in Preview for select workspaces and might be subject to change before general availability.

Use configuration import to promote asset type configuration between workspaces. The import process analyzes the bundle before applying changes, identifies new configuration, detects conflicts, and requires you to resolve conflicts before the import can continue.

  1. Go to Configuration > Import.
  2. Open the Configuration import type.
  3. Upload the configuration bundle.

    The import process validates the file syntax and bundle schema. If validation fails, the import is canceled and validation errors are shown.

  4. Wait for the import to reach the review state.

    The review state shows dependency and conflict analysis, including unresolved harvested technical asset type mappings, asset type conflicts, field conflicts, and missing reference list dependencies.

  5. Resolve harvested technical asset type dependencies.

    Map each imported harvested asset type reference to the matching asset type in the target workspace. If a required harvested dependency is unavailable, cancel the import.

  6. Resolve object and field conflicts.

    For asset type conflicts, choose whether to merge, replace, or keep both by renaming the imported asset type. Field conflict options depend on the conflict type and can include updating field configuration, keeping the existing field configuration, resolving display-as-badge conflicts, replacing duplicate tag fields, creating or mapping reference lists, or disabling a field.

  7. Apply the import.
The import creates or updates asset type configuration in the target workspace. The final status is completed, failed, or canceled.