> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Utility: Import and Export

> How to bulk import and export metadata, metrics, semantics, users, and lineage from the Command Center Utility page, and how to review the history of each run.

## Overview

The **Utility** page lets you import and export data and configurations in bulk, instead of editing records one at a time. It has two tabs, **Import** and **Export**. Each tab also keeps a history of past runs, so you can check whether a file was processed and how many records it contained.

## Navigating there

From the left-hand navigation:

```text theme={null}
Command Center → Utility
```

The page opens on the **Import** tab. Select **Export** to switch tabs.

![Utility Import tab with a data type dropdown, an Import button and the LIST OF IMPORT table](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/command-center/utility-import.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=53ab4c3a08cae225212288e27c4b4500)

## Supported data types

Import and export both work with the same five data types:

| Type | Use it for |
| - | - |
| **Metadata** | Metadata for all assets and attributes |
| **Metric** | Metric definitions and related information, including metric details, configurations, and relationships |
| **Semantics** | Semantic objects: Domain, Application, Product, Term, or Tag |
| **Users** | User accounts and user-related information for your organization |
| **Lineage** | Data lineage showing relationships and dependencies between data assets |

## Import

Use the **Import** tab to load data into Prizm from a file. Prizm accepts CSV and Excel (`.xlsx`) files.

1. Select **Command Center → Utility**. The **Import** tab opens.
2. In the dropdown under **IMPORT**, choose the type of data to import. If you choose **Semantics**, a second dropdown appears: choose **Domain**, **Application**, **Product**, **Term**, or **Tag**.
3. Select **Import**. An **Import** dialog opens and describes what that type imports.
4. Drag a file into the dialog, or select **Choose file**. The dialog's **Import** button stays disabled until a file is added.
5. Select **Import** in the dialog. To close it without importing, select **Cancel**.
6. Watch the new run appear at the top of **LIST OF IMPORT**, and check its **Status**, **Passed Records**, and **Failed Records**.

> [!NOTE]
>
> **Metadata** imports update existing metadata and create new entries for anything that does not exist yet. The **Metric** dialog also has a **Validated Query** toggle.

### File columns by import type

Prizm does not show a template or a required-field list in the Import dialog. The most reliable way to get a correctly shaped file is to start from an export of the same type: open the **Export** tab, choose the type, and select **Preview and Export** to see the columns, or export the file and edit it. The tables below list the columns that each export contains, in order, so you can build or check an import file against them.

> [!NOTE]
>
> The product does not publish which columns are mandatory. The tables mark the columns that were filled in on every record in a sample export (labelled **Always populated**) and the columns that were empty on some records (labelled **Can be blank**). Treat "always populated" as the minimum to supply, and keep ID columns exactly as exported when you re-import an edited file. A record that is rejected is counted in **Failed Records** for that run.

**Metadata**

| Column | Notes |
| - | - |
| `ID`, `Asset ID` | Identify the asset or attribute. Always populated. Keep unchanged when editing an export. |
| `Source ID`, `Source Name` | The source the asset belongs to. Always populated. |
| `Name` | The asset or attribute name. Always populated. |
| `Type`, `Sub Type` | For example `TABLE` or `ATTRIBUTE`. Always populated. |
| `Parent Asset ID` | The parent of an attribute. Blank for top-level assets. |
| `Is Incremental`, `Is Primary Key` | `true` or `false`. Always populated. |
| `Status` | For example `PENDING` or `VERIFIED`. Always populated. |
| `Description`, `Domain`, `Application`, `Product`, `Tag`, `Term`, `Owner` | Can be blank. |
| `Min Value`, `Max Value`, `Profile Type`, `Profile Scope` | Can be blank. |

**Metric**

| Column group | Columns |
| - | - |
| Identity | `Metric Detail ID`, `Metric ID`, `Metric Name`, `Metric Type`, `Metric Detail Type`, `Context` |
| Classification | `Category`, `Subcategory`, `Dimension`, `Description`, `Domain`, `Application`, `Product`, `Tag`, `Owner`, `Status` |
| Behavior | `Is Drift Enabled`, `Is Active`, `Allow Score`, `Is Positive`, `Is Aggregate`, `Weightage`, `Disable Scoring` |
| Thresholds | `Auto Threshold`, `Threshold Constraint` |
| Queries and rules | `Query`, `Failed Rows Query`, `Total Records Query`, `Properties` |
| Row capture | `Enabled Export Rows`, `Enabled Failed Rows`, `Enabled Total Records` |
| Linked term | `Term ID`, `Term` |
| Target asset | `Source ID`, `Source Name`, `Asset Type`, `Asset ID`, `Asset Name` |

`Metric Type`, `Metric Detail Type`, `Context`, `Allow Score`, `Weightage`, `Asset Type`, `Is Active`, `Auto Threshold`, `Threshold Constraint`, `Properties`, and `Status` were populated on every metric in a sample export. Thresholds are carried in the single `Threshold Constraint` column as structured JSON (a mode plus a list of rules), not as separate upper-bound, lower-bound, or condition columns. Edit that value with care, or change thresholds in the metric's own settings instead. The **Validated Query** toggle in the Metric import dialog controls whether queries are validated when the file is imported.

**Semantics**

All semantic types have `Name` and `Description`. The remaining columns depend on the type you choose:

| Semantic type | Columns |
| - | - |
| **Domain** | `Name`, `Description`, `Source`, `Parent ID`, `Status`, `Owner`, `Product`, `Glossary`, `Tag`, `Audiences` |
| **Application** | `Name`, `Description`, `Source`, `Owner`, `Status`, `Tag`, `Audiences` |
| **Product** | `Name`, `Description`, `Source`, `Domain ID`, `Owner`, `Status`, `Domain`, `Tag`, `Term`, `Audiences` |
| **Term** | `Name`, `Description`, `Status`, `Derived Type`, `Is Null`, `Is Blank`, `Is Unique`, `Is Primary Key`, `Contains`, `Synonyms`, `Owner`, `Product`, `Tag`, `Application`, `Glossary ID`, `Glossary Category ID` |
| **Tag** | `Name`, `Description`, `Type`, `Source`, `Native Query Run`, `Parent ID`, `Status`, `Is Masked Data`, `Owner`, `Source ID`, `Audiences` |

In a sample Domain export, `Name` and `Status` were populated on every record, while `Description`, `Source`, `Parent ID`, `Owner`, and the relationship columns were blank on some records. The other semantic types were not sampled the same way, so confirm their minimum fields by exporting a few records first.

**Users**

| Column | Notes |
| - | - |
| `Role Name` | The user's role. Always populated. |
| `Email` | The user's email address. Always populated. |
| `First Name`, `Last Name` | Can be blank. |
| `Is MFA Enabled`, `Is SSO Enabled`, `Is Active` | `true` or `false`. Always populated. |
| `Reports To` | The email address of the user's manager. Can be blank. |

**Lineage**

| Column | Notes |
| - | - |
| `ID` | Identifies the lineage link. Always populated. |
| `Lineage Source ID`, `From Source ID`, `To Source ID` | The sources on each side of the link. Always populated. |
| `From Asset ID`, `To Asset ID` | The assets on each side of the link. Always populated. |
| `From Qualified Name`, `To Qualified Name` | The full database, schema, and object names on each side. Always populated. |
| `From Asset Type`, `To Asset Type` | For example `TABLE`. Always populated. |
| `Is Custom` | `true` for links added manually rather than harvested from a source. Always populated. |

### List of imports

The **LIST OF IMPORT** table shows the most recent imports, up to 200. The count in the title is the total number of import runs.

| Column | Description |
| - | - |
| **Name** | The name of the file that was imported |
| **Type** | The kind of data in the import, for example `Metric_detail` |
| **Created At** | When the import was requested |
| **Start Time** | When processing started |
| **End Time** | When processing finished |
| **Duration** | How long processing took |
| **Status** | The state of the run, for example `COMPLETED` |
| **Total Records** | The number of records in the file |
| **Passed Records** | The number of records that were imported successfully |
| **Failed Records** | The number of records that were rejected |

A run can finish with a **Status** of `COMPLETED` and still have failed records. Always compare **Passed Records** and **Failed Records** to **Total Records**. If **Failed Records** is greater than zero, correct the rows that failed and import the file again.

The toolbar above the table has controls to filter, sort, and search the list. Its **More** menu includes **Select Columns**, **Download**, and **Reset Preference**.

## Export

Use the **Export** tab to download data from Prizm as a file.

1. Select **Command Center → Utility**, then select the **Export** tab.
2. Choose an **Export Type**.
3. Choose an **Export File Type**: **CSV** or **Excel**.
4. Fill in the fields that appear for the type you chose (see the table below).
5. Select **Preview and Export**. The button stays disabled until the required fields are filled in.
6. Find the new run in **Export Logs** to check its status.

![Utility Export tab with Export Type, Export File Type, Source and Assets fields and the Export Logs table](https://mintcdn.com/dqlabs/-llXdpktU4fg82jU/images/command-center/utility-export.png?fit=max\&auto=format\&n=-llXdpktU4fg82jU\&q=85\&s=d17d720c3ba6e63b2fc9587dd09c3930)

### Fields by export type

| Export Type | Additional fields |
| - | - |
| **Metadata** | **Source**, **Assets** |
| **Metric** | **Source**, **Assets**, **Metric Type**, **Metric** |
| **Semantics** | **Semantic Type** |
| **Users** | None. Choose the file type and export |
| **Lineage** | **Source**, **Assets** |

**Source** and **Metric Type** are multi-select lists with a **Select All** option, so you can export from several sources or metric types in one run.

**Metric Type** includes Auto, Query, Conditional, Behavioral, Lookup, Comparison, and Standalone Query.

**Semantic Type** is one of Domain, Application, Product, Term, or Tag.

### Export logs

The **Export Logs** table lists each export, with the total count in the title.

| Column | Description |
| - | - |
| **Name** | The generated file name, which includes the export type and a timestamp |
| **Type** | The kind of data that was exported |
| **File Type** | `CSV` or `Excel` |
| **Created At** | When the export was requested |
| **Start Time** | When processing started |
| **End Time** | When processing finished |
| **Duration** | How long the export took |
| **Status** | The state of the run |
| **Total Records** | The number of records in the export |

Each row has a **More** menu for additional actions. The toolbar above the table has the same filter, sort, search, and column controls as the import list.

## Permissions

The **Command Center – Utility Import/Export** permission controls this page. **View** lets a role see the page and its history. **Edit** lets a role configure or run an import or export. See [Role-Based Access Control](/security/rbac).

## Related pages

> **[Metrics](/concepts/metrics)**
>
> Importing and bulk editing metrics from the Metrics page

> **[Command Center Overview](/architecture/command-center/overview)**
>
> All Command Center sections


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.