Update sets

An update set is a recorded batch of changes — schema DDL, pages, forms, navigation, roles — captured while you work. It is nexp's unit of change: reviewable, exportable, and importable into another environment.

Capturing changes

Open Update Sets and create a set (or pick the active one). While a set is active, tracked changes you make in the schema designer and UI builder are recorded into it as ordered entries. When the piece of work is done, mark the set complete.

Anatomy

Field	Meaning
Name / description	What the change is
App	The app the changes belong to
State	`in progress` → `complete`
Entries	Ordered list of captured changes (DDL, config records)
Core version	Version of the platform the set was captured on

Export & import

Update sets serialize to JSON. From the UI use Export / Import; the same operations are available over the API:

# Export a completed update set
curl -H "Authorization: Bearer $TOKEN" \
  "$UPDATESET_API/v1/acme/update-sets/$SET_ID/export" > my-feature.json

# Import into another environment (as a draft)
curl -X POST -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d @my-feature.json \
  "$UPDATESET_API/v1/other-env/update-sets/import"

Imports are version-checked: if the source environment ran a newer core version than the target, the import is blocked (override with force=true once you've verified compatibility).

Good habits

One update set per unit of work — small sets promote and review cleanly.
Complete a set before exporting; in-progress sets keep accepting changes.
Promotion between environments of the same org is easier via releases, which move whole bundles.