Use import spreadsheet template - 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

Format spreadsheet columns according to your asset field types so data imports correctly.

  • Know the custom fields configured for your asset types. For details, see Define fields on asset types.
  • Test your import with a subset of data or a single row to identify errors before uploading the complete dataset.

The spreadsheet template contains all fields from the asset type configuration that can be imported.

Common field formatting rules:

  • xref: An alphanumeric identifier for assets within the workspace. Either provide a unique xref, or leave it blank for automatic generation. Xrefs must adhere to system-defined character limits.
  • Boolean: Enter values as TRUE or FALSE, regardless of UI labels like Yes/No.
  • Link: Use the format Name | URL (for example, Google | https://google.com). The name is optional.
  • Reference list: Provide the reference list's Object ID.
  • List: For single-select, provide the Code, Asset Object ID, or Asset xref of the reference list item. For multi-select, provide values as a semicolon-separated string without spaces: item1;item2;item3.
  • Tag: Separate multiple tags with a semicolon (;).
  • Date or Date-time: Use format <Date> or <Date>T<Time>. Conforms to your locale settings.
  • Decimal, Integer, Text, HTML: Enter values directly. If a field is not required and left empty, any configured defaults apply during import.
Note:
  • Field validations from asset type configuration are enforced. For example, Integer fields with range 10-50 reject values outside that range.
  • Excel does not support HTML formatting. Text entered in HTML fields imports as plain text.
  • Field types that cannot be imported: Relationship, Relation lookup, Counter, JSON, Asset path.

The following guidance applies to specific entity types:

  • Asset Types: Use the template with fields configured for your asset type. Include custom fields as required or optional per your configuration.

  • Models: Create hierarchical structures using xref and parentXref fields. Parent assets must exist before their children. Each xref must be unique within the workspace. For top-level assets, leave parentXref blank. For example:

    • Two-level: ParentModel (parentXref blank) → ChildModel (parentXref: ParentModel)
    • Three-level: ParentModel (blank) → ChildModel1 (ParentModel) → Component1 (ChildModel1)

    Plan hierarchy depth according to the maximum allowed for your asset type.

  • Policies: Include owner, related assets, and policy properties. Use the same template structure as models for multi-level hierarchies if applicable.

  • Reference Lists: The import adds items to an existing reference list. The list must exist before import; exactly one reference list can be targeted per import operation.

    • Template order: Parent (if hierarchical), Code (required), custom fields, Color (optional).
    • For hierarchical lists, parent items must exist before adding child items.
    • Color values must match available colors (case-insensitive): Amber, Aqua, Azure, Blush, Burgundy, Chocolate, Cobalt, Coffee, Cornflower, Denim, Ebony, Emerald, Grass, Hot Pink, Indigo, Lemon, Lilac, Lime, Mauve, Mustard, Orange, Peach, Rust, Sand, Scarlet, Sky, Slate, Spring, Stone, Sunshine, Tan, Teal, Violet, Wood. Multi-word colors (for example, "Hot Pink") require exact spelling.
    • Enable Trigger Workflows to run item-change workflows when items are added or updated.