# Edit a Computed File

Source: https://userguide.qualytics.io/container/computed-files/how-tos/edit/

Change the Select Expression, filter clause, grouping, lateral views, description, owner, or metadata of an existing Computed File.

> **Info: Related**
>
> - [Add a Computed File](https://userguide.qualytics.io/container/computed-files/how-tos/add/) to create a new one.
> - [Delete a Computed File](https://userguide.qualytics.io/container/computed-files/how-tos/delete/) to remove one.
> - [How It Works](https://userguide.qualytics.io/container/computed-files/deep-dive/how-it-works/) for validation and referencing rules.

## What You Can Change

| Field | Editable after creation? |
| --- | --- |
| Select Expression | Yes |
| Filter Clause | Yes |
| Group By Clause | Yes |
| Lateral Views | Yes |
| Description | Yes |
| Owner (Editors only) | Yes |
| Additional Metadata | Yes |
| Name | No (use the **Rename** action on the container) |
| Source File Pattern | No |
| Source datastore | No |

Source file pattern and source datastore are set at creation and cannot be changed. The name is not editable in this modal: to change it, select **Rename** in the same menu that opens **Edit** (see [Actions on Container](https://userguide.qualytics.io/container/actions-on-container/)). If you need a Computed File built on a different source pattern or datastore, create a new one and delete the old one.

## Who Can Edit

| Team permission | Can edit? |
| --- | --- |
| **Editor** | Yes |
| **Author** (owner) | Yes |
| Any other team permission | No |

Only users with the **Editor** team permission can reassign ownership. Users with the **Author** team permission can edit the Computed Files they own but cannot change the owner.

## Steps

**Step 1**: Locate the Computed File in the datastore's containers list and open its **Bulk menu** .

![Bulk menu button on a Computed File row](https://userguide.qualytics.io/assets/container/computed-files/how-tos/shared/step-1-bulk-menu.png)

**Step 2**: A dropdown appears with the actions available for that Computed File.

![Container bulk actions dropdown open on a Computed File](https://userguide.qualytics.io/assets/container/computed-files/how-tos/shared/step-2-settings-menu.png)

**Step 3**: Select **Edit** .

![Cursor on the Edit option in the settings menu](https://userguide.qualytics.io/assets/container/computed-files/how-tos/edit/step-3-edit-option.png)

**Step 4**: The Edit Computed File modal opens with the current values already filled in. Name and source file pattern are shown as read-only.

![Edit Computed File modal with the current values already filled in](https://userguide.qualytics.io/assets/container/computed-files/how-tos/edit/step-4-edit-modal.png)

**Step 5**: Change any of the editable fields (Select Expression, Filter Clause, Group By Clause, Lateral Views, Description, Owner, Additional Metadata).

![Edit modal with modified fields](https://userguide.qualytics.io/assets/container/computed-files/how-tos/edit/step-5-edit-fields.png)

**Step 6**: If you changed a clause, click **Validate** to confirm the new definition parses and every referenced field still exists. Running Validate is optional; if you skip it, Qualytics validates the definition as part of the Save request and surfaces any error inline.

![Validate button highlighted at the bottom of the Edit modal](https://userguide.qualytics.io/assets/container/computed-files/how-tos/edit/step-6-validate-button.png)

**Step 7**: Click **Save**.

![Save button highlighted after successful validation](https://userguide.qualytics.io/assets/container/computed-files/how-tos/edit/step-7-save-button.png)

> **Warning: Fields will be marked as missing**
>
> If your changes would drop a field that an active quality check or anomaly depends on, Qualytics blocks the save and opens the **Fields will be marked as missing** warning listing the affected fields. Click **Review Expression** to go back and adjust the clause, or **Proceed Anyway** to save with the dropped fields. The affected fields are marked as missing and their quality checks and anomalies are preserved so they reactivate automatically if the fields reappear.

**Step 8**: A success message confirms the update. A new entry is added to the container's **Timeline**, and the clause change collapses behind a **View changes** control that opens the side-by-side comparison for that clause. Lateral Views changes are recorded on the Timeline but do not open the comparison.

![Success message confirming the Computed File update](https://userguide.qualytics.io/assets/container/computed-files/how-tos/edit/step-8-success-message.png)

> **Note: Editing triggers a profile**
>
> Changing any clause (Select Expression, Filter Clause, Group By Clause, Lateral Views) causes Qualytics to re-profile the Computed File immediately after save: a synchronous slim profile refreshes field statistics right away, and a full asynchronous profile follows in the background. Existing quality checks are preserved; anomalies raised against the older version stay in the anomaly history for auditability.

*Last updated: October 19, 2026.*