Multi Search

Multi search fields let users select multiple records from another form. The stored value is a list of selected record identifiers.

Use a multi search field when one record should point to several related records, such as a project linking multiple tasks or an incident linking multiple affected assets.

Basic Settings

Setting	Description
Name	The field label shown to users. It is required and should describe the relationship clearly
API Name	The stable technical name used by data APIs, scripts, formulas, imports, and integrations. It is required
Required	Requires users to select related records before the record can be saved
Readonly	Shows selected records but prevents users from changing them
Disabled	Makes the field unavailable for normal use
Hidden	Stores selected values while hiding them from normal form pages

Multi Search Field Config

Setting	Description
Source Form	The target form that provides selectable records. It is required
Relation Data Scope	Optional Studio script that filters which target records users can select
Placeholder	Prompt text shown before users select records
Modal Title	Title shown in the record selection dialog
Search Placeholder	Prompt text shown in the search box inside the selection dialog
Validate Trigger	Controls when selection validation runs: when the value changes, when the field loses focus, or when the record is submitted
Input Status	Adds a visual status to the field, such as warning or error
Invalid Selection Message	Custom message shown when one or more selected records are invalid or unavailable
Field Color	Sets the display color used for the field
Help Text	Helper copy shown near the field. Use it to explain which records users should choose

Common Examples

Scenario	Source Form
Project selects related tasks	Task
Incident selects affected assets	Asset
Campaign selects target customers	Customer
Release selects included requirements	Requirement

Relation Data Scope

Use Relation Data Scope when this field should only allow a scoped set of records from the source form.

Examples:

• Only active assets
• Only customers in the current campaign segment
• Only records matching the current child-row category

The script is bound to this source field and runs before the selection dialog loads target records. It returns a relationDataFilter condition that uses target-form field API names.

Do not configure this filtering rule on the target form's page events. See Relation Data Scope for the payload and response contract.

Configuration Tips

Tip	Description
Use plural names	Names such as Related Tasks or Affected Assets make multi-selection clear
Check the target identifier	The target form should have a clear identifier so users can recognize records
Add a useful modal title	A title such as Select Affected Assets helps users understand the selection dialog