A persistent entity's form is organized as tabs → sections → rows → field placements. A row has up to 12 columns. A field occupies part of that width: 12 is a full row, 6 is half, and 4 is one third.
Example: arrange a ENTITY_NAME form
Assume Content already contains name, sku, price and description.
- Open Admin editor and select ENTITY_NAME.
- In Content fields, use + for any field that is not placed yet.
- On the canvas, drag
skubesidename. The drop target shows whether the field will join a row or start a new one. - Select the row. In Properties → Row preset, choose Halves for two equal columns, or Wide + narrow for a larger first field.
- Keep
descriptionin a full-width row. Select its placement and set Width (columns) to 12 / 12. - Use Add section to introduce another group, then select it to enter Title and Description.
Move and size elements
| Control | Result |
|---|---|
| Drag a field by its canvas surface | Move its placement within or between rows |
| Drag a row by its free edge | Move the complete row |
| Drop above or below a row | Start a new row |
| Drop beside a field | Add a column; a full row is redistributed to make room |
| Width (columns) | Set the selected placement's width from 1 to 12 |
| Row preset and Row alignment | Set widths and horizontal/vertical alignment |
| Move earlier / Move later | Reorder a selected element without dragging |
| Move field to row / Move field to tab | Move a placement through Properties |
Rows cannot exceed 12 columns. A field can be placed only once across the whole layout. Hidden or removed Content fields cannot be placed. Validation explains what to fix before saving.
Heading, Heading + description and Divider add visual structure; they do not create database columns. Boolean placements also offer Compact control.
Removing a row keeps its fields
The row's trash button removes the row and its placements. It does not delete Content fields or database data. Unplaced fields remain visible in Other fields and can be added back. To change a field's visibility, use its Content settings; removing a placement is not a way to hide data or restrict access.
Use Undo and Redo while arranging the form. Continue with preview and languages.
Unplaced fields and visibility
In Admin editor, unplaced fields remain visible under the canvas in Other fields, so you can place them again. In the generated form, Other fields (N) is a flat disclosure button at the bottom, collapsed by default. Removing a placement does not remove the field or its values.
Hidden hides a field from both list and form; Readonly keeps it readable during editing. There are no independent Show in table / Show in form switches. Moving a placement to Other fields organizes the form; it neither restricts access nor removes the field from the API.