Import models, policies and reference lists

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
2025

This feature enables efficient bulk import of models, policies, and reference lists in the Data Integrity Suite.

This capability supports asset creation, hierarchy and relationships, and property updates in one streamlined operation:

  • Models: including hierarchical structures and owner/related asset relationships.
  • Policies: including owner and related assets, with property updates.
  • Reference Lists: including items and updates to existing lists.

To import, follow these steps:

  1. Navigate to Configuration > Import. This will open the interface for managing your import tasks.
  2. To start a new import, click on the Import button.
  3. Choose the Import Type: Models, Policies, or Reference Lists.
  4. The default Import Action available is Add/Update.
  5. From the drop-down menu, select the Type you wish to import. You may also include a Description.
    Note: The Columns tab in the side panel lists all the required and optional fields necessary for importing the selected asset. When you download the spreadsheet template, these fields will appear as column headers, ensuring that your data aligns correctly for import.
  6. You can turn on the Trigger workflows toggle to initiate workflows associated with the asset type.
    Note: During the import process, the system will display available workflows in the Triggered Workflows tab in the side panel. If no workflows are available, this will be indicated in the side panel, and the toggle to trigger workflows will be disabled. Click on the workflow links to view detailed information in a secondary panel, which can be closed to continue the import.
  7. Download the spreadsheet template by clicking on the Download Spreadsheet Template option. This template will include the required fields and columns based on the type you select. Mandatory columns for required fields are shown in bold.
  8. 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, as they are essential for successful creation. Each imported file is limited to a maximum size of 100 Megabytes. Uploaded files will be retained for 90 days.
  9. Upload the file by either browsing and selecting a file from your computer or by dragging and dropping your data file directly.
    Tip: Ensure your file is in XLSX, XLS, or CSV format.
  10. Once the file is uploaded, the system will perform several validation checks.
  11. If validation fails due to errors such as missing required fields, an invalid reference, or a depth limit exceeded, an error message will be displayed, highlighting the problematic records.
  12. Click on the View errors option or check the specific error messages for each row in the Errors tab located in the side panel.
  13. You can also re-upload only the rows that did not pass validation for correction.
  14. After finalizing the template, click on the Import button to start the process. Upon successful import, the system will display a confirmation message.
  15. Navigate back to the Import page, where you can track the progress of your import through various status indicators, including In Progress, Completed, Partial, and Failed. The system offers real-time updates throughout the import process. To see the most recent status, refresh the page.
  16. In the Import Type column, you can click the context menu next to the asset import job to access details about the job. From there, you can view information, export records with errors, export imported records, or download the original file.

Import file format

Key structure guidance:

  • Models: include hierarchical relationships (parent/child), ownership, and property values.
  • Policies: include owner, related assets, and policy properties.
    Note: For Models and Policies, the same import template supports adding assets at multiple levels, up to the maximum depth defined.
  • Reference Lists: include list identifiers and reference item details.

    • The import operation adds reference items to an existing reference list. This feature provides a consistent way to bulk-create items for a single reference list. The import requires a target reference list and a template that defines the information needed for each item.

    • Key concepts to understand before importing:
      • The reference list must already exist; the import adds items to that list.
      • Only one reference list can be targeted per import operation.
      • For hierarchical reference lists, parent items must exist before adding child items.
      • A color value for each item is optional and may be supplied from an available color list.

    • The import template specifies the information needed to create each reference item. It includes all custom fields on the reference list and marks required fields. The basic order of the template is:

      • Parent (if applicable): If the reference list is hierarchical and you are adding child items, include a column to identify the parent item. Preferred values can be a name or the parent’s Code. If the name is not available, an ID (object ID or Xref) may be provided.
      • Code: The unique code for the reference item (required).
      • Custom fields: Include all defined fields on the reference list (required or optional as indicated by the template).
      • Color(optional): The color name for the item. The color name must map to an existing color in the available colors list. Color name matching is case-insensitive.
        Note:
        • The color list may include multi-word names (for example, "Hot Pink"). Ensure the exact two-word name is used when applicable.
        • List of available colors are:
          • 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
        • If you enter a color name that is not in the allowed color list, your asset creation will be rejected. The error message will display the list of colors you may use. If you do not provide a color, no action is required.

    • Enable the Trigger Workflows option when a reference list item is added or updated.

      • If you enable it, item-change workflows for either the subject or the object will run and create a workflow instance for each added relationship.
      • If you do not enable it, no workflows will be triggered for the imported reference items.

To know how to update existing assets, see topic: Update existing assets using import.

Multi-level import for models and policies

Refer to the following process of creating hierarchical structures with multiple levels in a single import operation, using the xref and parentXref fields in your spreadsheet templates.

Key points:
  • Ensure all xref values are unique within your workspace.
  • Parent assets must exist before their children to establish correct hierarchy.
  • Use the parentXref to specify the direct parent of each asset. For top-level assets, leave the parentXref blank.
  • The hierarchy can be extended beyond three levels, depending on the maximum depth allowed for the asset type. Ensure that each xref and parentXref are correctly assigned to maintain the hierarchy integrity.
  • When populating the parentXref field, ensure it contains the xref of the direct parent asset.
  • Plan your hierarchy depth according to the maximum allowed for the asset type.

Example: Hierarchical structure in spreadsheet

When creating a hierarchical structure for import, understanding the roles of parent and child assets is essential.

  • Parent Asset: The higher-level asset that acts as a container or grouping for other assets. It does not have a parent itself (its parentXref is blank). Example name:Parent Model.

  • Child Asset: An asset nested under a parent asset. It references its parent via the parentXref field, which should contain the xref of its immediate parent. Example names:Child Model 1 (child of Parent Model), Component 1 (child of Child Model 1), Part 1.1 (child of Component 1).

The following examples illustrate how to represent two-level and three-level hierarchies. The asset names such as ParentModel, RootModel, etc are just example names for assets at different hierarchy levels.

Two-level hierarchy

This example shows a parent model with a single child model. The xref and parentXref fields are used to define the hierarchy:

xref parentXref Name
ParentModel   Parent Model
ChildModel ParentModel Child Model

Three-level hierarchy

This example shows a root asset with a first-level child, which in turn has a second-level child. The parentXref for each asset points to its immediate parent:

xref parentXref Name
ParentModel   Parent Model
ChildModel1 ParentModel Child Model 1
Component1 ChildModel1 Component 1
Part1.1 Component1 Part 1.1

Ensure that parent assets (ParentModel and ChildModel1) are created before their children to maintain hierarchy integrity.