Editor’s Corner: Pro Tips for Working with Multiple Choice in ArcGIS Online

The multiple choice input type in ArcGIS Online opens up new possibilities for data collection, allowing editors to select multiple answers for a single question. While it’s easy to add to a form, there are some important nuances to keep in mind. Understanding how it stores, displays, and even counts data can help you avoid surprises later. In this article, we’ll share 5 tips to help you get the most out of multiple choice.

1. Labels vs Codes: How Data is Displayed
2. Reuse Multiple Choice Across Maps
3. How Choices Drive Field Length
4. Include Other: Custom Responses Made Easy
5. Min, Max, and Required: How Validation Works

          Take it further: DIY Other for Combo Boxes and Radio Buttons

1. Labels vs Codes: How Data is Displayed

Before you start building forms with multiple choice, it helps to understand how the values are stored behind the scenes. When an editor selects one or more answers, those are saved together in a single text (string) field.

Here are a few important details to keep in mind:

• Label: This appears in the choice list on the form.
• Code: Values are stored using the coded value.
• Comma-separated values: When more than one value is selected, they’re stored as a comma-separated list with no spaces (for example: 1,2,3).
• Why it matters: The way things display is different than we see with other questions like combo box. When using multiple choice, labels appear only on the form, while codes are displayed in places like tables and pop-ups.
• Example: A damage assessment form includes the choices Rocks, Mud, and Fallen Trees, with codes 1, 2, and 3. If an editor selects the first two, the values are saved in the field as 1,2. That’s what shows up in the table and pop-up as well.

Pro tip: For easy to read tables and pop-ups, consider using the same value for both the label and code when creating choice lists.

For an even more user-friendly pop-up, follow the steps in this article to transform those comma-separated values into a clean list.

2. Reuse Multiple Choice Questions Across Maps

Unlike a combo box or radio buttons, the choices you configure for a multiple choice question aren’t saved to the layer as a domain. Instead, they’re initially stored in the form for the map you’re working in. The good news is that there is a way to reuse them in other maps. First, let’s look at how the field appears:

Layer: Fields used in multiple choice questions appear as a standard string field with no associated domain or coded value list.

Item details page: If you inspect the field properties on the Data tab, the field appears just like any other string field without a predefined list of choices. You’ll see the same thing in places like the table, or when configuring filters.

Map: The multiple choice question and its choices exist in the form inside the map where you created them.

Why it matters: while multiple choice displays a list of choices in the form, behind the scenes it’s storing multiple coded values together in a string field. If you add the layer to another map, the field looks like a regular string field. When you set up forms with multiple choice questions, you may want to use them again. To do that, save the form to the layer. This stores all the properties that have been configured on the layer, including the form, multiple choice questions, and choice lists.

Pro Tip: After you set up the form, save it to the layer using the options menu in the Layers pane. That way when you add the layer to a map, the form, multiple choice questions and choice lists all come along with it.

3. How Choices Drive Field Length

When configuring a multiple choice field, it’s important remember how the selected values are stored. Since multiple answers are saved in a single field, the field needs to be long enough to hold every possible selection at the same time. By default, the field length is 1000 characters, which in most cases should be plenty. But if you want to shorten it or you’re working with a very long list of choices, keep these things in mind:

• Field length: The field must be long enough to store all possible choices, plus commas.
• Character countdown: The character counter behaves a little differently here than it does for other choice lists. It adds up the length of the entire choice list, plus commas, rather than just the choice you’re currently entering.

Pro Tip: Set your field length to accommodate the sum of all values plus commas.

4. Include ‘Other’: Custom Responses Made Easy

Multiple choice is the first input type in ArcGIS Online to offer a built-in ‘other’ option:

• How it works: Check a box to add ‘other’ to the list of choices. When selected, editors are prompted to enter a custom value.
• Where it goes: The custom value is stored in a separate field. You can pick an existing field (from a list of existing string fields with no domains) or let ArcGIS Online create a new one for you.
• Required input: when they select ‘other’, editors must enter a value. It can’t be left blank.

Pro Tip: To keep your data neatly organized, add a new string field in advance with a descriptive field name where you can store ‘other’ values. Select that from the dropdown when selecting an existing field.

5. Min, Max, Required: How Validation Works

You can control how many choices editors must (or can) select using the following settings. However, these settings behave a little differently here than they do for different input types. Let’s break it down:

Minimum

• What it does: Sets the fewest number of choices an editor must pick.
• If not required: The minimum only applies if they select something. If they skip the question, the form can still be submitted.
• If required: Editors must select at least the minimum number of choices before submitting the form.

Maximum

• What it does: Sets the most choices an editor can pick.

Required

• What it does: Makes the question mandatory. Editors must select at least one choice (or the minimum, if set).

A note about ‘Other’

• Values entered in the ‘other’ field do not count toward the minimum or maximum.
• Why? Think of it this way: The main choices are stored in one field, while other responses are stored in a separate field. Validation rules only apply to the original field.

Pro Tip: When setting minimum or maximum values, remember that ‘other’ responses are not included in the count.

Take it Further: DIY ‘Other’ Values for Combo Box or Radio Buttons

While combo boxes and radio buttons don’t offer the built-in option we see with multiple choice, you can create a similar experience that allows you to capture custom responses with a few extra steps:

1. Include ‘other’ in your list of choices: this will serve as the ‘other’ option.
2. Create a custom field: Add a new text field where you’ll store custom values.
3. Use conditional visibility: Set the new field to appear in the form only when ‘other’ is selected in the previous question.
4. Make it required: By default, the field will only be required when visible. That way, when an editor checks the ‘other’ value, they’ll be prompted to enter a value in the input box that appears.

Pro Tip: Build your own ‘other’ option when you want to let editors enter custom values for questions that appear as combo boxes or radio buttons.

Summary

The multiple choice input type is a powerful addition to forms in ArcGIS Online. By understanding how the data is stored, putting some thought into choice lists, and leveraging the built-in ‘other’ option, you can create forms that are robust and user-friendly. And with a few extra steps, you can bring the same flexibility to different choice input types as well. We hope you gained some insights that will help you make the most of this new feature. As always, hop on over to Esri Community to share your feedback and ideas with us.