Skip to content
MoltaroMoltaroMoltaro Docs

Display fields

The Display fields tab defines read-time string values that table and card surfaces can render — computed labels, badges, and summaries that make grids and cards readable without opening every record.

Display fields are display-only: they are not searchable, sortable, filterable, or editable, and they do not add stored fields to the data model.

Ready example: Full name

Section titled “Ready example: Full name”

Create a Display Field named Full name and keep its final Otherwise rule. Use this value template:

{LastName} {FirstName}

Replace LastName and FirstName with the exact field keys from the entity schema. The result is evaluated when a record is read and can then be selected as a Table column or Card item.

How a display field works

Section titled “How a display field works”

Each display field has a key, a display name, and an ordered rule list. Every rule pairs a DSL condition with a value template; rules are evaluated top to bottom, the first matching condition renders its template, and the list always ends with an Otherwise rule so a value is always produced. Condition and template syntax is documented in the expression language reference.

Three display mechanisms, three purposes

Section titled “Three display mechanisms, three purposes”
  • Display name and subtitle rules (Overview tab) compute how the record is labeled everywhere — see Presentation and statements.
  • Display fields (this tab) add extra read-time values that table and card surfaces can place as columns or items.
  • Stored fields (Schema tab) hold the actual data — see Fields and schema.

For derived stored values, choose a Calculated Field when the supported formula language is sufficient, or a C# before-save mutation function when the derivation needs procedural logic. Neither is a replacement for a Display Field: they persist data, while a Display Field renders read-time text.

API clients replace the complete ordered Display Field rule set through PUT /api/workspace/admin/entity-definitions/{entityDefinitionId}/display-fields. Use the installation-local Configuration OpenAPI document for the exact request schema and current RowVersion contract.

Where to go next

Section titled “Where to go next”