> ## 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.

# Resetting an Entity

> Clear an entity’s mapping and return it to its default state

## Overview

Reset clears an entity's mapping and returns it to its default state, so you can rebuild it from scratch. A reset is recorded in the entity's change history, and you can undo it by reverting to the version before it.

> [!NOTE]
>
> **Required permissions**
>
> * **Manage Production Pipelines** or **Manage Dev Pipelines**: Update
> * **Manage Silver Entities** or **Manage Gold Entities**, for the entity's layer: Update
>
> Without both, the **Reset** button doesn't appear. See [roles and permissions](https://support.entegrata.com/administration/user/roles-and-permissions.md#feature-reference) and [permission dependencies](https://support.entegrata.com/administration/user/permission-dependencies.md).

## Resetting an Entity

**1. Open the Entity**

Open the entity in the [mapping editor](https://support.entegrata.com/data/pipeline/data-mapping-editor.md).

**2. Select Reset**

Click **Reset** in the editor toolbar, next to **Validate** and **Publish**.

**3. Confirm**

The **Reset entity?** dialog lists what will be cleared. Click **Reset** to continue.

## What a Reset Changes

* **All sources, data maps, and field mappings on the entity are removed.**
* **Entegrata entities return to their standard definition.** The entity gets the current standard fields on a single **Default** map. Custom fields you added to the entity are removed.
* **Custom entities keep only their ID field**, on a single empty **Default** map.
* **Unsaved changes in the editor are discarded**, along with any Automap suggestions you hadn't saved.
* **A Reset entry is added to the entity's change history.**

The entity itself, its pipeline, and its layer stay the same.

> [!NOTE]
>
> A reset doesn't publish. Your running pipeline keeps using the last published mapping until you publish again. See [Publishing Mappings](https://support.entegrata.com/data/pipeline/publishing-mappings.md).

## Undoing a Reset

**1. Open History**

With the entity open, click **History** at the top of the page.

**2. Find the Entry Before the Reset**

The **Reset** entry stores the entity as it was **after** the reset. The next older entry holds the mapping you had before.

**3. Revert**

Click **Revert** on that earlier entry, enter a reason, and click **Revert entity**.

See [Change History and Revert](https://support.entegrata.com/data/pipeline/change-history.md) for details.

> [!WARNING]
>
> Only changes recorded in change history can be restored. If the entity has no entry before the **Reset** entry, the earlier mapping can't be restored from history.

## Related Topics

> [card] [Change History and Revert](https://support.entegrata.com/data/pipeline/change-history.md)
>
> Review earlier versions and restore one

> [card] [Data Mapping Editor](https://support.entegrata.com/data/pipeline/data-mapping-editor.md)
>
> Rebuild the entity's mapping

> [card] [Automap in the Mapping Editor](https://support.entegrata.com/data/pipeline/automap-entity.md)
>
> Get suggested mappings for the reset entity

> [card] [Publishing Mappings](https://support.entegrata.com/data/pipeline/publishing-mappings.md)
>
> Put the new mapping into production


## Related topics

- [Change History and Revert](https://support.entegrata.com/data/pipeline/change-history.md)
- [Release Notes](https://support.entegrata.com/release-notes/release-notes.md)


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