Skip to main content
The Data Model Editor is a master-detail form for mapping values onto a data model. A tree view on the left shows the model’s structure — its objects, arrays, and unions — while a detail editor on the right lets you fill in the leaf properties of whichever container you select. This makes even deeply nested and repeating structures straightforward to populate.

How It Works

The editor derives its form from the data model’s schema so the form always matches the model’s shape:
  1. The data model’s schema definition is converted into a standard JSON Schema.
  2. The JSON Schema is transformed into a strongly-typed field structure that is easy to render as a form.
  3. The form is rendered as a master-detail layout — a tree of containers plus a detail editor for the selected container’s fields.

Containers and Leaves

The editor distinguishes between the two kinds of fields in a schema:
  • Containers — objects, arrays, and unions that hold other properties. These appear in the tree view so you can navigate the structure.
  • Leaves — terminal fields that resolve to an input (a resource reference, a dropdown selector, a text value, and so on). These appear in the detail editor for the container you have selected.

Unions

A union is a discriminated field whose available properties change based on a selection — for example, a value that can be an object, an array, or a plain string. The editor lets you pick the active type and then edit only the properties valid for that choice.

Arrays

Arrays are fully supported: add, edit, and remove items, each rendered with the detail editor for the array’s item type.

Working With the Editor

1

Open the data model

Open the data model you want to populate in the template builder.
2

Navigate the structure

Use the tree view to move between containers — objects, arrays, and unions.
3

Map the leaf values

Select a container and fill in its leaf properties in the detail editor. For unions, choose the active type first; for arrays, add and edit items.
Leaf fields can reference flow resources, so you can map live values onto the model rather than hard-coding them.

Next Steps

Variables

Compute and reuse values across your flow

Live Page Services

Expose server-side data to your pages