Custom Text Field

Tips & examples

Text built from an expression, so the wording can change with the record or the signed-in user.

When to use

A sentence that has to combine several values, or change wording depending on the data.

Examples

‘3 of 12 tasks complete’ assembled from two counts.

Avoid

Building long formatted documents in one expression — a Markdown Field keeps the content readable.
Using it for a single unmodified column value, which a Text Field shows with less configuration.

Use instead

Markdown Text — Use instead when the text needs headings, lists or emphasis.

Properties

Editor properties

Configure these in the Application Designer property panel. Group headings mirror the editor where possible. Data Source is where the element gets its rows or field binding (a view/query, a connector operation, or a parent form field). References appear only for view-backed sources and map foreign-key ID columns to readable labels from another view.

Required

TextrequiredCustom expression: Configuration for text.
Default: none

Optional

StyleoptionalKey-value map: Configuration for style.
Default: none

Sizing

No size of its own: dropped at the platform default of 1 × 1 grid cells and resized on the page.

Composition

Where you can place it

Drag this element into one of these containers:

Sample configuration

Minimal example — required fields only ↕

1
2
3
4
5
{
  "config": {
    "text": "@@expression:'value'"
  }
}

1
2
3
4
5
6
7
8
{
  "config": {
    "text": "@@expression:'value'",
    "style": {
      "exampleKey": {}
    }
  }
}