A view is a saved grid layout for a table’s record list — which columns show, in what order, with what default sort and filter. Every table ships with several system views, and users can also build their own.

System view types

  • Active / Inactive / All — the baseline views every table gets automatically.
  • Associated View — the layout used when a table’s records are shown as a subgrid on a related record’s form.
  • Lookup View — the simplified column set shown when searching for a record in a lookup field’s dropdown.
  • Quick Find View — not a display layout exactly, but the set of searchable columns used when a user types into the search box. Covered in depth next chapter.

Admins/makers can create as many additional public views as needed; individual users can also save their own personal views, which only they see.

Editable grids

Any view can be set to render as an editable grid instead of a static read-only list — letting users update values directly in the grid (like a spreadsheet) without opening each record. This is a per-view toggle and works well for bulk data entry/cleanup scenarios, but isn’t appropriate for every table (anything with complex conditional business rules is often better edited on the full form).

Keep default views lean. A common mistake is cramming a view with every column “just in case.” Default views should show only what’s needed for the task at hand — extra columns slow down load time and make the grid harder to scan. Build a second, more detailed view for power users instead of overloading the default one.

Filtering and sorting

Views support static filter criteria (e.g. “Status = Active”) set at design time. For filters that need to change based on who’s looking or what they just searched, that’s a job for Advanced Find (power users building ad-hoc views) rather than editing the system view itself.