Use a Combobox Selection in a Query or Flow
Pass what an agent picks in a Combobox to Get Records, another component's query, a flow dialog or a record update, using the right value output.
A support agent picks the customer's account in a Combobox. The rest of the flow depends on that choice: the contact list narrows to that account, a later Get Records finds its open cases, a flow dialog logs a new case for it, and the new case is saved against it. Each destination expects the selection in a specific shape, and the Combobox offers one output per shape.

Before you start
A Combobox with its options set up. See Build Combobox Options.
The Combobox's API Name. This page uses
AccountPicker.
Which output to use
Every output below updates each time the agent changes the selection. The examples assume a multi-select Combobox on Case priorities where the agent picked High, then Medium.
Value
Text
Medium;High
One value for a filter with Equals, a record field, a subflow or dialog input. Also the format of a multi-select picklist field.
Value Collection
Text collection
Two items: Medium, High
A Get Records filter with the In operator, a Loop, a collection input.
Value Comma Separated
Text
'Medium','High'
A query filter built in a formula, with IN. Output only.
Value Collection Serialized
Text
["Medium","High"]
An element that expects the list as JSON text. Rarely needed: Value already holds a multi-selection in one text.
Selected Option / Selected Options
Record / Record collection
The selected record or records
Query and Variable data sources, when the next element needs the record itself.
A few rules that explain most surprises:
Value holds each option's value, never its label. For a Picklist data source that is the picklist API value. For a Query data source it is the field mapped to Value in Data Mappings, the record Id by default.
The most recent pick comes first.
On a single-select Combobox, each output holds one value: Value is
High, Value Collection has one item, Value Comma Separated is'High'.Value Comma Separated wraps each value in single quotes and escapes any apostrophe inside a value (
'O\'Brien'). The quotes are part of the text, so it only fits inside a query condition.
Steps
Step 1 sets up the account picker. Steps 2 to 5 are independent: build the ones your flow needs.
Set up the account picker
Add Avonni Combobox to a screen and set its API Name to
AccountPicker.In the Component Builder, set Label to
Accountand Data Source to Query on the Account object.In Data Mappings, map Label to the account Name and Value to its Id.
Turn on Show Search so the agent can type a name.
Value now holds the Id of the picked account.
Filter another component's query on the same screen
The contact Combobox below the account picker should list only that account's contacts.
Create a Text formula resource named
ContactFilter:
Add a second Combobox with a Query data source on Contact.
In its Filters, open the value type menu, choose Mapped, and select
ContactFilter.
The contact list stays empty until an account is picked, then reloads on every change. When the first Combobox is multi-select, use "AccountId IN (" & {!AccountPicker.valueCommaSeparated} & ")" instead. Filter Data Tables with Multi-Select Comboboxes builds the same pattern for a Data Table.
Use the selection in Get Records
After the screen, add a Get Records element on Case:
Single selection: Account ID Equals
{!AccountPicker.value}.Multiple selection: Account ID In
{!AccountPicker.valueCollection}.
Need another field of the picked account, its Industry for example? Run Get Records on Account with Id Equals {!AccountPicker.value} and read the field from that record.
Open a flow dialog with the selection
To log a case as soon as the agent picks an account:
In the Component Builder, open the Interactions tab and add a Change interaction of type Open Flow Dialog.
In API Name, select the flow to open. It needs a Text input variable, here
accountId.Under Input Variables, set Name to
accountId, type{{current.value}}in Value (as text, with the resource toggle off), and set Type to Text.

{{current.value}} is read at the moment the agent picks. A flow resource such as {!AccountPicker.value} in this field is read when the screen loads, before any pick, so the dialog would receive an empty value. Open Flow Dialog covers the other dialog settings.
Pass the selection to a subflow or a record update
After the screen, the selection is an ordinary flow value:
Subflow: set the subflow's Text input variable to
{!AccountPicker.value}, or its Text collection input to{!AccountPicker.valueCollection}.Update Records or Create Records: set the case's Account ID to
{!AccountPicker.value}.A multi-select picklist field takes Value directly, since it stores its values separated by semicolons too.
Troubleshooting
Related tutorials
Filter Data Tables with Multi-Select Comboboxes: the Data Table filter, with the empty selection handled.
Keep Combobox Selections When Users Go Back: store the selection in a variable and bring it back on a revisit.
Implement Dependent Picklists in Comboboxes: link two picklist comboboxes without a formula.
Expression Syntax in Interactions: the dynamic values interaction fields accept.
Was this helpful?
