Edit a Computed Join
This page walks through editing an existing Computed Join. For the conceptual overview, see How Computed Join Works.
Permissions
You need Editor permission on the left datastore, or Author permission plus ownership of this Computed Join. See Computed Join Permissions for the full matrix.
What can be edited
| Field | Editable? |
|---|---|
| Name | (use the Rename action on the container) |
| Left Datastore / Container | |
| Right Datastore / Container | |
| Join Type | |
| Left / Right Field | |
| Left / Right Prefix | |
| Select / Filter / Group By Clause | |
| Description | |
| Owner | (Editor only) |
| Additional Metadata |
The left and right containers themselves are immutable after creation. To change them, delete the Computed Join and recreate it.
Edited elsewhere. The Edit Computed Join modal covers the join definition, description, owner, and additional metadata. Other container-level settings live on separate surfaces:
- Name - use the Rename action on the container.
- Tags - use the tag picker on the container detail page.
- Volumetric and freshness tracking, automation flags - use the container's Monitoring modal.
- Incremental identifier - use the container's Settings modal (only exposed for schema-based source containers).
Steps
Step 1: Open the Container settings menu from the Computed Join's card or detail page.
Step 2: In the dropdown, click Edit.
Step 3: The Edit Computed Join dialog opens. Adjust the fields you want to change. As you edit:
- Changing a Prefix rewrites every matching column reference in the Select Expression automatically.
- Changing the Select Expression to remove a field that has active quality checks triggers a Fields will be marked as missing warning panel.
Step 4: Click Validate. A Validation Successful message appears if the SQL parses and the schema resolves.
Step 5: Click Save to apply the changes. A success message appears.
When Fields Will Be Marked as Missing
If your edit removes a field that has active quality checks or anomalies, the dialog switches to an amber panel listing each affected field with its quality-check and anomaly counts. Two options appear at the bottom:
- Review Expression returns to the form so you can adjust the Select Expression.
- Proceed Anyway applies the edit.
For what happens to the dropped fields' checks and anomalies afterwards, see Field Changes on Inputs. For the literal server message, see Removed fields warning on Save.