Edit a Computed Table
Change the SQL query, description, owner, or metadata of an existing Computed Table.
Related
- Add a Computed Table to create a new one.
- Delete a Computed Table to remove one.
- How It Works for validation and referencing rules.
What You Can Change
| Field | Editable after creation? |
|---|---|
| Name | |
| Query | |
| Description | |
| Owner (Editors only) | |
| Additional Metadata | |
| Source datastore |
Name and source datastore are set at creation and cannot be changed in the UI. The Edit modal does not expose a Name input. If you need a Computed Table under a different name or on a different datastore, delete the existing one and create a new one.
Who Can Edit
| Team permission | Can edit? |
|---|---|
| Editor | |
| Author (owner) | |
| Any other team permission |
Only users with the Editor team permission can reassign ownership. Users with the Author team permission can edit the Computed Tables they own but cannot change the owner.
Steps
Step 1: Locate the Computed Table in the datastore's containers list and open its Bulk menu .
Step 2: A dropdown appears with the actions available for that Computed Table.
Step 3: Select Edit .
Step 4: The Edit Computed Table modal opens with the current values already filled in.
Step 5: Change any of the editable fields (Query, Description, Owner, Additional Metadata).
Step 6: If you changed the Query, click Validate to confirm the new SQL parses and every referenced table and column exists. Running Validate is optional; if you skip it, Qualytics validates the query as part of the Save request and surfaces any error inline.
Step 7: Click Save.
Dropped Fields Warning
If your changes would drop a field that an active quality check or anomaly depends on, Qualytics blocks the save and opens the Dropped Fields Warning modal listing the affected fields. Click Review Query to go back and adjust the SQL, 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 History panel with a View Query Changes action that opens the From/To diff for this revision.
Editing triggers a profile
Changing the Query causes Qualytics to re-profile the Computed Table 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.