Container Edit Mode
On a View page, the Edit Mode of the Form widget in the page template decides how users edit the record's fields: not at all (None), one field at a time (Inline), or all at once with a page-level Save (Full). Container Edit Mode lets a single Fields container on a View form choose its own edit mode instead, so one page can mix read-only, inline-editable, and fully editable sections.
Everything about building the form — containers, fields, widgets — works exactly as described in Forms. This page covers only the container-level edit mode.
There are two levels of control:
- The Form widget in a View Page Template — its Edit Mode setting (None / Inline / Full) applies to every container of the form it hosts.
- A per-container setting (in each Fields container's ⚙ settings on a View form). Options add Inherit (the default) — follow the hosting Form widget.
Because containers default to Inherit, existing forms keep behaving exactly as they always have until an administrator picks a concrete edit mode for a container.
Edit mode options
| Option | What the container does at runtime |
|---|---|
| Inherit | Container level only, and its default. Use the Edit Mode of the Form widget that hosts the form in the current page template. |
| None | Fields render read-only. Users cannot edit them from this container. |
| Inline | Fields render read-only with an edit control per field. Users edit one field at a time, and each change is saved as soon as it is confirmed. |
| Full | Fields render with their editors. Changes collect on the page and are saved together with the toolbar Save button. |
Field permissions still apply in every mode: a field the user cannot update stays read-only even in an Inline or Full container.
Configure it
- Open Design Studio → Forms and open a form whose Form Mode is View.
- Click the ⚙ icon on a Fields container.
- Under Edit Mode, choose Inherit, None, Inline, or Full.
- Save the form.
The setting appears only for Fields containers on View forms. Create, Edit, Quick Edit, Edit Relation, and Sticker forms don't show it, and neither do Standard, Custom, Text, and Separator containers.
For each Fields container on a View page, the edit mode is resolved as:
Container (if not Inherit) → Form widget Edit Mode in the hosting template
A container's own concrete setting always wins. An Inherit container follows the template, so the same form can behave differently in two templates that host it with different edit modes.
The Save button
The Save button in the View page toolbar is page-level. It appears when any form on the page is fully editable — either the hosting Form widget's Edit Mode is Full, or at least one Fields container resolves to Full.
For example, a template whose Form widget is set to Inline normally shows no Save button. If that form has one container set to Full, the page shows Save, and that container's changes are saved with it while the other containers keep editing inline.
Example
A Purchase Order View template hosts its form with Edit Mode Inline. The form has three Fields containers:
| Container | Container Edit Mode | Result on the View page |
|---|---|---|
| Order Details | Inherit | Inline — follows the template |
| Approval Record | None | Read-only, even though the template allows inline editing |
| Delivery Notes | Full | Editors shown; the toolbar shows Save for this section's edits |
┌─────────────────────────────┐ ┌─────────────────────────────┐
│ Order Details (Inline) │ │ Approval Record (None) │
│ Vendor Acme Ltd ✎ │ │ Approved By J. Smith │
│ Amount 12,500 ✎ │ │ Approved On 12-Oct-2026 │
└─────────────────────────────┘ └─────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Delivery Notes (Full) │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Deliver to Gate 2 between 9 and 11 am │ │
│ └─── ──────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘
When to use it
- Inherit (default) — the container behaves like the rest of the form. The safe choice unless this section genuinely needs to differ.
- None — lock a section that users should only read on this page, such as approval or audit details, while the rest of the form stays editable.
- Inline — allow quick single-field corrections in an otherwise read-only or fully editable form.
- Full — let users edit a whole section in one go and save it with the page Save button, while other sections stay read-only or inline.
Notes
- The setting applies only to View forms.
- Containers saved before the setting existed have no value and behave as Inherit.
- Inherit is stored as an empty value, so a schema export omits
editModefor those containers. A container with a concrete mode exportseditModeasNone,Inline, orFull, and schema import restores it.
Next Steps
- Build the form itself: Forms
- Host the form in a View template and set its Form widget Edit Mode: Page Template Editor
- Keep view and edit identical — no layout shift on inline edit: Render Read-Only Editor for All Attributes
- Position field labels (above / left / below): Form Input Label Alignment
- See how forms render for end users: Client-Side Experience