Skip to main content

Form View

Configuration reference: Formulário

Overview​

The Form view renders a dynamic form for creating and editing records. Fields are organized into tabs and sections, with support for conditional visibility, validation, and custom layouts.

This view is the primary interface for detailed data entry and record editing.

Form layout​

Forms are structured hierarchically:

Tabs​

The top level of organization. Each tab appears as a clickable header. Use tabs to separate different aspects of a record — for example, "General", "Details", "Attachments".

Sections​

Within each tab, fields are grouped into sections. Each section can have a label and contains one or more fields.

Rows​

Sections can arrange fields in rows with one or two columns:

  • Single column — Each field takes the full width
  • Two columns — Fields are arranged side by side

Special sections​

  • Toolbar section — A toolbar row with action buttons
  • Special section — Custom layout areas for embedded content

Field display​

Each field in the form renders according to its component type:

  • Text fields show as text inputs
  • Select fields show as dropdowns
  • Date fields show as date pickers
  • File fields show as upload buttons
  • Linked Select fields show as searchable dropdowns
  • Linked View fields show as embedded sub-views
  • Checklist fields show as interactive task lists
  • And so on for all 19 component types

Required fields are marked with a visual indicator. Read-only fields display their value but cannot be edited. Hidden fields are excluded from the form entirely.

Conditional visibility​

Fields can be shown or hidden based on other field values. For example:

  • Show "Delivery Address" only when "Requires Delivery" is checked
  • Show "Discount Percentage" only when "Has Discount" is selected
  • Show "Custom Date" only when "Date Type" is set to "Custom"

Visibility conditions are configured per field in the form view settings. Each rule has an action:

  • Show IF: the field only appears when the condition is met.
  • Hide IF: the field disappears when the condition is met.
  • Required IF: when the condition is met, the field stays visible and becomes required in this form; when it is not met, the field keeps its configured behaviour.

The operators and the value editor follow the type of the chosen column, like the view filters: a date opens a date picker (with "Between", "Today", "Past"…), an option list shows its options, a number compares as a number and a checkbox uses "Is true" or "Is false", with no value.

A field can depend on its own value; in the list it is marked with "· this field". For example, "Show IF Order is not empty" on the "Order" field keeps it hidden until the "Create order" button fills it. A value the user clears by hand does not hide the field mid-edit.

The Depends on list starts with two context entries, before the form columns:

  • Current user: compares with the person filling in the form. The operators are "is", "is not" and "is in"; with "is in" you pick several people from the organisation.
  • Role: compares with that person's effective role in the workspace (Owner, Administrator, Editor, User, Viewer or Kiosk). A kiosk terminal always counts as Kiosk.

These conditions combine with the others through AND/OR, just like column conditions. Hiding a field in the form does not hide it from the data: the table, the API and exports still show the column.

Validation​

  • Required fields must have a value before the record can be saved.
  • Unique fields (text fields configured for uniqueness) are validated against all existing records, with optional case-insensitive and whitespace-trimmed comparison.
  • Date constraints can restrict to future dates only or enforce a min/max range.
  • Numeric constraints can enforce min/max values.

When opening a record​

Each view chooses which of the table's forms opens on Add and Edit, and at what size: S, M, L (the usual size), XL or Ecrã inteiro (full screen). With Predefinido the table's default form opens. On a phone the dialog always opens as a sheet, so the size only counts on desktop; with full screen chosen, the full-screen button in the dialog header is hidden.

It is set in each view's configurator, under Comportamento › Formulário, card "Ao abrir um registo". If the chosen form is deleted, the view quietly falls back to the default. Opening the same record from elsewhere (a link chip in another table, notifications or workflows) keeps the default form and size.

Form actions​

The form toolbar can include custom action buttons linked to workflow executions. These appear at the top of the form and trigger configured automations when clicked.

The toolbar can be collapsed from the button on its bottom edge and restored from the Show toolbar entry in the record's ⋯ menu; when set to Collapsed by default, it opens collapsed; the toolbar itself and each of its items accept the same visibility rules as fields (Show IF / Hide IF), in the toolbar's properties panel.