> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/visual-picker/save-multiple-picks-to-a-picklist-field.md).

# Save multiple picks to a picklist field

Let users tick several Visual Picker cards in a screen flow and save them to a multi-select picklist field, using the Checkbox type and the Value output.

Your Account has a multi-select picklist field, Product Lines, and you want customers to keep it up to date in a short screen flow. Each product line is a card, the customer ticks the ones they use, and the flow saves the ticks to the field in one go.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FRlIl9CCWoONQ2pVv5hzv%2Fvisual-picker-save-multiple-picks-to-a-picklist-field-result.png?alt=media" alt="Visual Picker showing five product line cards from a multi-select picklist field, with Hardware and Services ticked"><figcaption><p>Each value of the picklist field is a card the customer can tick.</p></figcaption></figure>

## Before you start

* The Account object has a multi-select picklist field. This page uses **Product Lines** (`Product_Lines__c`); use your own field and values.
* Your screen flow receives the Account Id in a `recordId` variable. See [How to pass your current RecordID in your screen flow](https://docs.avonnicomponents.com/flow/tutorials/tips-and-tricks/how-to-pass-your-current-recordid-in-your-screen-flow.md).
* The [Avonni Flow Screen Components](https://docs.avonnicomponents.com/flow/getting-started/installation-and-licenses-management.md) package is installed and you have its permission set.

## Steps

{% stepper %}
{% step %}

### Add a Visual Picker to a screen

Open a **Screen** element, drag the Avonni **Visual Picker** onto it and give it the API Name `Product_Lines_Picker`. In the **Properties** tab, set **Label** to `Which product lines do you use?`.
{% endstep %}

{% step %}

### Set Type to Checkbox

Set **Type** to **Checkbox**. It sits right under **Label**.

This is the setting that allows several picks. The default, **Radio**, keeps one card selected at a time, even when the cards come from a multi-select field.
{% endstep %}

{% step %}

### Load the cards from the picklist field

Set **Data Source** to **Picklist**, choose the object `Account`, and in **Picklist Field** pick **Product Lines**. The picker draws one card per value of the field.

If the field's values differ by record type, set **Record Type**. **Sort Order** sets the card order: **Ascending**, **Descending** or **Default Order of Field**.

Picklist cards can't carry an image. Use **Size** **Small** or larger, so the value's label shows on the card.
{% endstep %}

{% step %}

### Save the picks with Update Records

After the screen, add an **Update Records** element:

* **How to Find Records to Update and Set Their Values**: **Specify conditions to identify records, and set fields individually**.
* **Object**: Account. **Filter**: `Id` **Equals** `{!recordId}`.
* **Set Field Values**: **Product Lines** ← `{!Product_Lines_Picker.value}`.

**Value** returns the ticked values in one text, separated by semicolons: `Hardware;Services`. That is how Salesforce stores a multi-select picklist, so it goes into the field as is.
{% endstep %}

{% step %}

### Save and test

Save and activate the flow, then run it from an Account. The screen shows one card per product line. Tick two cards and click **Next**.

Open the Account: **Product Lines** shows exactly the two values you ticked. Run the flow again and tick a single card: the field now holds only that one, because Update Records replaces the whole field.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Value Collection** returns the same picks as a Text collection. It is the right output for a Loop, not for a field: a multi-select picklist field takes the semicolon text that **Value** returns.
{% endhint %}

## Troubleshooting

<details>

<summary>Only one card can be ticked at a time</summary>

**Type** is **Radio**, the default. Set it to **Checkbox** in the **Properties** tab, right under **Label**.

</details>

<details>

<summary>Flow Builder doesn't offer the picker's output for the field</summary>

You picked **Value Collection**, which is a collection and can't fill a single field. Pick **Value** under the `Product_Lines_Picker` component instead.

</details>

<details>

<summary>The field is emptied when the customer ticks nothing</summary>

An empty **Value** clears the field. Turn on **Required**, or set **Min** to `1` under **Advanced Options**, so **Next** stays blocked until at least one card is ticked.

</details>

<details>

<summary>The cards are empty tiles</summary>

**Size** is **Xx-Small** or **X-Small**, which show only an avatar. Picklist cards have no avatar, so nothing is drawn. Use **Small** or larger.

</details>

## Related tutorials

* [Limit and pre-select Visual Picker choices](https://docs.avonnicomponents.com/flow/tutorials/components/visual-picker/limit-and-preselect-visual-picker-choices.md): require between two and three picks, with one ticked in advance.
* [Picklist data source](https://docs.avonnicomponents.com/flow/component-builder/data-sources/picklist.md): every picklist option, including dependent values.
* [Visual Picker](https://docs.avonnicomponents.com/flow/flow-components/visual-picker.md): what each output variable returns.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/flow/tutorials/components/visual-picker/save-multiple-picks-to-a-picklist-field.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
