Skip to main content
Editing a blueprint creates or updates a version; it does not silently replace the live definition. Use a draft for work in progress, then publish after you validate the full output.

​
Open the correct version

From the entity detail page:
  • Select Edit to start from the current supported version.
  • Select Edit Draft when the page reports that a recent draft already exists.
Only supported client blueprints and imported entities can be edited in this workspace. Editing can also be unavailable while a deployment is in progress.
Editing and publishing catalog versions requires blueprint management access. Data access controls can require additional access to change Role Access.

​
Make and validate changes

1

Update the documentation

Revise the description and tags so they describe the new behavior.
2

Edit the SQL

Use the Source explorer to insert catalog names, then format the SQL.
3

Run the query

Validate the SQL and inspect the returned rows. Any SQL change invalidates the previous validation.
4

Review columns

Confirm names, data types, descriptions, and classifications. Pay special attention to removed or renamed columns.
5

Review access

If Role Access is available, confirm that the intended roles remain selected.
6

Save or publish

Select Save Draft to continue later. Select Publish & Deploy only after the output is ready for downstream use.
The editor reports No changes detected when the new version matches the baseline. It also blocks publishing when required permissions or validation are missing.

​
Publish safely

Before selecting Publish & Deploy:
  1. Review lineage for downstream dependencies.
  2. Compare the old and new result grain.
  3. Check for renamed, removed, or retyped columns.
  4. Verify that PII and other masking classifications still apply.
  5. Save a draft if another reviewer should inspect the change first.
Publishing progresses through version creation, staging, and application. Do not open another editor for the same entity while this work is in progress. If the app reports that the version was saved but the upgrade did not finish, open blueprint versions. A target may already be staged or in progress. Resolve that state before publishing another version.
Do not retry deployment blindly. A saved or staged version can survive a later error, and a second attempt can create unnecessary version history.
Last modified on September 16, 2026