Input
Type identifier:
inputCategory: Experience Blocks
Description
Interactive data-entry block with component variants for text/date input and optional Flow triggers.
Schema Summary
The Input block has the fields below, plus component-specific fields.
Required core fields:
type: "input"input: datumReference
Optional core fields:
colorvariant: "soft"lookupFilterstates
Component-specific fields are discriminated by component.
Component Variants
Component | Variant-specific fields |
|---|---|
|
|
|
|
| no additional fields |
|
|
Not set (omitted) |
|
Properties
Property | Type | Required | Notes |
|---|---|---|---|
|
| Yes | Shared block identifier. |
|
| Yes | Block discriminator. |
|
| Yes | Bound datum target: an entity context, or a For Each item that is a Record (see Editable Rows). |
|
| No | Variant discriminator. |
|
| No | Input colour override. |
|
| No | Input style variant. |
|
| No | For an input bound to a relationship field: further limits which Records can be picked. See Lookup Filter. |
| Array of states | No | Optional state-specific overrides. |
The Input block also supports the shared style/layout/data props.
Lookup Filter
When input is bound to a relationship field, lookupFilter limits which Records the lookup offers, on top of the field's own lookup filter. Both apply.
Condition values can be literals, page datums (datumReference, e.g. a Region chosen elsewhere on the page), or the bound Record's fields (path, relative to the bound field when it starts with @). Relative paths start from the bound field's place in the datum, so an input bound to lines.0.product reaches the invoice's customer with @^^^.customer.
While a value it reads is empty, the lookup offers no Records and asks for it first, such as Select Customer first, or Select a value first for a page datum.
In Studio, set it under Lookup filter in the Input settings. It is shown when the input is bound to a relationship field.
States
State entries follow the shared state shape and support partial input overrides.
Pseudo states for TextField, TextArea, and InlineCalendar:
hoverfocusdisabledreadonly
DateField has no pseudo states.
Custom states:
InlineCalendar:dateSelected- other input components: none
Minimal Valid Example
{
"id": "input-1",
"type": "input",
"input": {
"type": "datumReference",
"referenceId": "currentEntity"
}
}