Select
Select selects one or more values from static options, a Custom URL, or a Model data source. It participates in the state, validation, and submission boundary of its Form.
1. When to use it
Typical uses:
- Status, type, and enum values
- Searchable long option lists
- Options returned dynamically by a backend
2. Add and configure
- Add Select to the Fields slot of a Form Section.
- Set a stable, unique Field Key / Name that matches the backend DTO property.
- Configure the component properties below, then add Required, Help Text, Full row, or conditions as needed.
- Check the initial value and layout in Design Preview, then use Form Validate / Submit to test the full data path.
3. Main properties
| Property | Purpose |
|---|---|
| Options | Defines where selectable data comes from and how it is mapped. |
| Data Source | Defines where selectable data comes from and how it is mapped. |
| Multiple | Enables or disables this behavior. |
| Selectable Count | Limits the allowed count, length, or value range. |
| Enable Search Box Input | Enables or disables this behavior. |
| Disabled | Enables or disables this behavior. |
Common properties such as Field Key, Required, Help Text, Full row, and Visible When come from the Form field contract. The table highlights the settings most relevant to Select.
4. Form value and backend contract
Submitted value: A stable option value in single mode, or an array of option values in multiple mode.
"engineering"
["engineering", "product"]
The example shows the data shape only. The API must still validate type, range, and authorization against its business DTO.
5. Validation, conditions, and interactions
Every field can use Form properties such as Required, Visible When, Disabled When, Required When, Dependencies, and Clear When Hidden. Conditions improve interaction but never replace backend validation or authorization.
Component capabilities: Supports onChange so a selection change can continue a Page Interaction.
6. Recommendations
Recommendations: Keep option values stable for backend enums or IDs. Labels may be localized, but must not be used as business keys.
Return to the Form overview for layout, validation, submission, drafts, and backend protocol guidance.