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

# Managing Data Types

> Learn how to create, edit, and archive data types (entities) in your Entegrata data pipelines

## Overview

Data types (also called entities) are the foundation of your data pipeline. Each data type represents a business concept like customers, orders, or products. In Entegrata, you define data types and map them to your source data, creating a unified view across all your systems.

This guide covers the complete lifecycle of managing data types in your Entegrata instance.

## Understanding Data Types

A data type in Entegrata represents:

* A unified business concept (e.g., "Customer", "Invoice", "Product")
* The fields and structure of that concept
* Mappings to one or more data sources
* Access controls determining who can view the data
* Lineage information showing data flow

## Creating a New Data Type

<Steps>
  <Step title="Navigate to Data Types">
    From the admin portal navigation, select **Data Mappings** or **Pipelines** to access the data type management interface.

    <Frame>
      <img src="https://mintcdn.com/entegrata/sWO-t3fu8JP8xl73/images/pipelines/entity_list_view.png?fit=max&auto=format&n=sWO-t3fu8JP8xl73&q=85&s=0433d6a33887720c661b8af61e627251" alt="Pipeline navigation menu showing Data Types section" width="2734" height="1484" data-path="images/pipelines/entity_list_view.png" />
    </Frame>
  </Step>

  <Step title="Click Create New Data Type">
    Click the **New Data Type** or **Create Entity** button in the top right corner of the data types list.

    <Frame>
      <img src="https://mintcdn.com/entegrata/514kJn1kETJv_yXN/images/pipelines/create_pipeline_button_active.png?fit=max&auto=format&n=514kJn1kETJv_yXN&q=85&s=c95c9d63eaa73a41e3247cbb751dda68" alt="Data types list view with Create button highlighted" width="2546" height="529" data-path="images/pipelines/create_pipeline_button_active.png" />
    </Frame>
  </Step>

  <Step title="Configure Basic Information">
    In the creation dialog, provide:

    * **Name**: A clear, singular name for your data type (e.g., "Customer", "Order")
    * **Description**: A brief explanation of what this data type represents
    * **Icon** (optional): Select an icon to help identify this data type visually
    * **Category** (optional): Group related data types together

    <Frame>
      <img src="https://mintcdn.com/entegrata/FZ7uPvdDC2XYN2d6/images/pipelines/create_entity_modal.png?fit=max&auto=format&n=FZ7uPvdDC2XYN2d6&q=85&s=2e7e4467f9a7c3abcef66e70e15b9b56" alt="Create data type dialog with fields filled" width="1614" height="942" data-path="images/pipelines/create_entity_modal.png" />
    </Frame>
  </Step>

  <Step title="Create the Data Type">
    Click **Create** to save your new data type. You'll be taken to the entity list view.
  </Step>
</Steps>

## Editing an Existing Data Type

### Updating Basic Properties

<Steps>
  <Step title="Select the Data Type">
    Find the entity you want to edit in the list view.
  </Step>

  <Step title="Open Edit Modal">
    Click the **Edit** option under the entity's option menu.

    <Frame>
      <img src="https://mintcdn.com/entegrata/sWO-t3fu8JP8xl73/images/pipelines/entity_list_edit_option.png?fit=max&auto=format&n=sWO-t3fu8JP8xl73&q=85&s=7e211a790794b851dbe8913473374387" alt="Edit entity menu option" width="2786" height="446" data-path="images/pipelines/entity_list_edit_option.png" />
    </Frame>
  </Step>

  <Step title="Modify Properties">
    Update any of the following:

    * Name
    * Description

    <Frame>
      <img src="https://mintcdn.com/entegrata/FZ7uPvdDC2XYN2d6/images/pipelines/edit_entity_modal_empty.png?fit=max&auto=format&n=FZ7uPvdDC2XYN2d6&q=85&s=e345d35d27763676a08adea66aa83db9" alt="Edit entity details" width="1666" height="894" data-path="images/pipelines/edit_entity_modal_empty.png" />
    </Frame>
  </Step>

  <Step title="Save Changes">
    Click **Save** to apply your changes. These updates take effect immediately and don't require republishing.
  </Step>
</Steps>

### Modifying Field Structure

To add, remove, or change fields in your data type, see the [Field Management](/data/pipeline/field-management) guide.

### Updating Mappings

To change how source data maps to your data type fields, see the [Mapping Fields](/data/pipeline/mapping-fields) guide.

## Archiving Data Types

Archiving removes a data type from active use without deleting historical data.

<Warning>
  Archiving a data type will:

  * Stop all data processing for this data type
  * Hide it from most users' views
  * Preserve historical data and lineage
  * Allow restoration if needed

  Archived data types can be unarchived, but the process may require reconfiguration.
</Warning>

<Steps>
  <Step title="Open the Data Type">
    Navigate to the data type you want to archive.
  </Step>

  <Step title="Archive Option">
    Click the **Archive** option in the options menu for the entity.

    <Frame>
      <img src="https://mintcdn.com/entegrata/sWO-t3fu8JP8xl73/images/pipelines/entity_list_archive_option.png?fit=max&auto=format&n=sWO-t3fu8JP8xl73&q=85&s=88e13c4e82b656ba78d6aacfe5838328" alt="Edit Options menu with Archive option" width="2756" height="546" data-path="images/pipelines/entity_list_archive_option.png" />
    </Frame>
  </Step>

  <Step title="Confirm Archive">
    Review the warning message and confirm that you want to archive this data type.

    <Frame>
      <img src="https://mintcdn.com/entegrata/FZ7uPvdDC2XYN2d6/images/pipelines/archive_entity_confirm_modal.png?fit=max&auto=format&n=FZ7uPvdDC2XYN2d6&q=85&s=d2b0588b8e96007f9ea9bfa4f4c2f430" alt="Edit Archive confirmation modal" width="1694" height="642" data-path="images/pipelines/archive_entity_confirm_modal.png" />
    </Frame>
  </Step>

  <Step title="Complete Archive">
    Click **Archive** to complete the process. The data type will be moved to the archived status.
  </Step>
</Steps>

## Best Practices

<Tip>
  **Naming Conventions**

  * Use singular nouns (e.g., "Customer" not "Customers")
  * Be descriptive but concise
  * Avoid technical abbreviations
  * Use consistent casing (recommend Title Case)
</Tip>

<Tip>
  **Organization**

  * Group related data types with categories
  * Use clear, business-friendly descriptions
  * Maintain a logical hierarchy (e.g., Orders before OrderItems)
  * Document dependencies between data types
</Tip>

<Tip>
  **Lifecycle Management**

  * Start with draft status and test thoroughly
  * Archive instead of delete when possible
  * Document why data types are archived
  * Regularly review and clean up unused data types
</Tip>

## Troubleshooting

### Cannot Archive Data Type

**Issue**: The archive option is grayed out or unavailable.

**Solutions**:

* Check if you have admin permissions
* Verify no active dependencies exist
* Ensure the data type is published (only published types can be archived)

### Archive Failed with Dependencies

**Issue**: Archive fails with message about dependent objects.

**Solutions**:

* Check for reports or dashboards using this data type
* Look for other data types with relationships to this one
* Remove or update dependencies first, then archive

### Unarchive Not Restoring Data

**Issue**: After unarchiving, no data appears in the data type.

**Solutions**:

* Verify source connections are still active
* Check that credentials haven't expired
* Republish the mapping to restart data processing
* Review field mappings for any broken references

## Related Topics

<CardGroup cols={2}>
  <Card title="Field Management" icon="list" href="/data/pipeline/field-management">
    Learn how to add and configure fields in your data types
  </Card>

  <Card title="Mapping Fields" icon="arrow-right-arrow-left" href="/data/pipeline/mapping-fields">
    Map source data to your data type fields
  </Card>

  <Card title="Access Controls" icon="shield" href="/data/pipeline/access-controls">
    Control who can view and edit your data types
  </Card>

  <Card title="Publishing Mappings" icon="upload" href="/data/pipeline/publishing-mappings">
    Deploy your data type mappings to production
  </Card>
</CardGroup>
