---
title: "Fields that store multiple values from a prompt list"
slug: "fields-that-store-multiple-values-from-a-prompt-list"
updated: 2026-02-27T19:51:43Z
published: 2026-02-27T19:51:43Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Fields that store multiple values from a prompt list

[Custom fields](/v1/docs/custom-fields) have different configurations based on the type of data stored.

Before you create a custom field, consider the data it stores and how you will use that data in Slate.

This article will focus on one of the four types of custom fields:

- [Fields that store free-text values](/v1/docs/fields-that-store-free-text-values)
- [Fields that store a single value from a prompt list](/v1/docs/fields-that-store-a-single-value-from-a-prompt-list)
- Fields that store multiple values from a prompt list
- [Fields that store a yes/no value](/v1/docs/fields-that-store-a-yesno-value-bit-prompt)

## Create Multiple Values Prompt List Fields

To create a field that stores multiple values:

1. Go to **Database**→ **Fields**.
2. Select **New Field.**
3. Configure the following settings:
  - **Status:**Active
  - **Scope Category:**Select a [scope category](/v1/docs/fields-settings#scope-category) from the list.
  - **Scope:**Select a [scope](/v1/docs/fields-settings#scope) from the list.
  - **ID:**Enter a unique ID for the field. 🔔 No uppercase, spaces, or special characters.
  - **Name:**Enter a name for the field.
  - **Field Type:**Multiple Values
  - **Prompt:**Select a [prompt](/v1/docs/prompts) from the list.
  - **Ordered:**Unordered Values 💡 Ordered values are used for fields grouped using a [replicate block](/v1/docs/replicate-blocks).
  - **Appendable:**Choose whether incoming data replaces or appends to existing data. See the [next section](/v1/docs/fields-that-store-multiple-values-from-a-prompt-list#replacing-vs-appending-values) for more detail on this setting. [![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/11202532703003.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/11202532703003.png)
4. Select **Save.**

## Replacing vs. appending values

You can collect information for a field that stores multiple values. Data can come into this field from various sources, like an inquiry form, an event registration form, or uploaded data.

Carefully consider how a field should save data when new information is submitted. For example, an academic interests field can have the following values stored for a record:

| **Academic Interests** | Biology |
| --- | --- |
|  | English |
|  | Theatre |

#### Replace existing values upon form submission or dataset import

If the field is configured to replace existing values upon form submission or dataset import, new data that comes into this field from a form submission or a dataset upload will **delete** any existing values and save only the most recently submitted or uploaded values:

| **Academic Interests** | ~~Biology~~ |  |
| --- | --- | --- |
|  | ~~English~~ |  |
|  | ~~Theatre~~ | Form Submission |
|  |  | **Academic Interests** |
|  | Biology | Biology |
|  | Chemistry | Chemistry |
|  | Sociology | Sociology |

#### Append to existing values upon form submission or dataset import

If the field is configured to append to existing values upon form submission or dataset import, new data that comes into this field from a form submission or a dataset upload will **preserve** any existing values and add new values upon form submission or source import:

| **Academic Interests** | Biology | Form Submission |
| --- | --- | --- |
|  | Chemistry | **Academic Interests** |
|  | English | Biology |
|  | Sociology | Chemistry |
|  | Theatre | Sociology |

#### Single value field?

Custom fields configured to [store a single value](/v1/docs/fields-that-store-a-single-value-from-a-prompt-list) always replace the value with the most recently submitted or uploaded data.

> [!CAUTION]
> 🔔 Important!
> 
> You should never change the following settings after a field is in use:
> 
> - **Scope**
> - **ID**
> - **Prompt**
> - **Value**
> 
> Changes to any of these can result in inconsistent and inaccurate data.