idea Multiple choice option in Field Maps in ArcGIS Field Maps Ideas

Multiple choice option in Field Maps

ZoevdbAT — Wed, 06 Oct 2021 15:30:52 GMT

I'd like to have a multiple choice option in Fieldmaps. The current version of Field Maps (Oct 2021) has limited options for data collection. When collecting an attribute value I sometimes need people to fill in multiple values form the same domain list. I'd like them to be able to select multiple values from the combobox or radio buttons.

I'm hoping this function will be added with the new function of creating elements form scratch (kinda like the different options in de survey123, preferably the Multiple Choice) but also not like that, because I need them to use my domain values and not create a new field.

Does anyone have a smart workaround for this in the meantime?

Re: Multiple choice option in Field Maps

AarushiJhatro — Tue, 12 Oct 2021 22:29:55 GMT

A big YES to this post as I run into the same issue frequently.

My work around was to create an individual field for each value in the domain list. I edited each field to have a 'Yes' or 'No' domain list, and used the switch option on smart forms to make it easier for surveyors to select. However, this is a very limited solution, especially if you have a long domain list.

Hoping we have the ability to select multiple choices in a list soon.

Re: Multiple choice option in Field Maps

ZoevdbAT — Wed, 13 Oct 2021 10:00:48 GMT

@AarushiJhatro That's a very time consuming solution. But I might use this for my smaller domain lists in the meantime, thanks!

Re: Multiple choice option in Field Maps

AlfredBaldenweck — Thu, 14 Oct 2021 20:14:58 GMT

Something that may also work for you is using Survey123 to edit the feature after you take the geometry.

Use Survey123 with existing feature layers—ArcGIS Survey123 | Documentation

Re: Multiple choice option in Field Maps

cbp-geus — Wed, 14 Dec 2022 08:08:33 GMT

This is really a vital option for our use of the ArcGIS Field Maps data collection in our organisation.

We are hoping to use this app for our geologist’s field work, but we need to be able to make multiple choice selection one or more vital information for certain attributes such as lithology description, mineralogy composition, fossil classification etc. from one data point collection.

Re: Multiple choice option in Field Maps

BradBolton1 — Tue, 24 May 2022 13:04:46 GMT

I'd also like to comment the need for selecting multiple options in a list. We have staff needing to select one or more permit violations when visiting many different parcels.

Re: Multiple choice option in Field Maps

Woodpecker — Thu, 08 Sep 2022 13:53:16 GMT

I come across that kind of issues quite often as well. The best thing I could think of so far, is using a bit of Arcade magic to put together a workaround. The script looks something like this:

// $feature["Options"] will be a field with the domain list. Make sure to add a domain "Clear list" to the choices // $feature["Options_List"] is a field that will store the concatenated values var selection = $feature["Options"] var thisFieldValue = $feature["Options_List"] if (IsEmpty(thisFieldValue)) { return selection } else if (selection == "Clear list") { return '' } else if (Find(selection, thisFieldValue) != -1) { return thisFieldValue } else { return thisFieldValue + ', ' + selection }

Basically what you are doing is adding domains in the 'Options List' based on the selection in 'Options' field. When adding text in the Options list, they will be separated by comma.

You will also need to add 'Clear selection' which will simply erase everything in the Options list. This allows user to clear the field if they accidentally selected the domain they didn't want.

You will also need to prevent a single domain being added to the Options list multiple times (lines 13 and 14).

Hope this helps

Re: Multiple choice option in Field Maps

AdewaleFalaye — Mon, 07 Nov 2022 15:35:09 GMT

@Woodpecker can you please elaborate more on this. I have tried this and its not working for me. It is still picking single option on the domain list. After picking the second option, it switched from the first option selected. Thanks in advance.

Re: Multiple choice option in Field Maps

DavidPuckettSEA — Thu, 10 Nov 2022 23:43:25 GMT

An up-vote for multi-select fields.

We have also implemented the 'different field for each option' approach but users don't love it. @Woodpecker if you'd be willing to elaborate on your solution we would certainly all benefit. The logic makes sense to me as I am a developer but I am brand spanking new to Field Maps.

Re: Multiple choice option in Field Maps

Woodpecker — Fri, 03 Feb 2023 10:30:50 GMT

@DavidPuckettSEA @AdewaleFalaye

How I set this up, is having 2 different fields for each multiple choice question.

First one will have the list of values/domains assigned to it from which a user will need to pick. Let's call it values.

The second one will be an empty text field. You will need to apply the calculations to this field (Calculated expressions). Let's call this one multiple_choice_list.

var values = $feature["values"] // Let's imagine the values field includes domains ["red", "blue", "green", "yellow"] var multiple_choice_list = $feature["multiple_choice_list"]

With the code below, anything that a user selects in a 'values' field, will be added to the 'multiple_choice_list' field.

if (IsEmpty(multiple_choice_list)) { return values } else { return multiple_choice_list + values }

Sure, every time user changes the selection in 'values' field, the value in that field will change accordingly - it won't store multiple selections. But at the same time, it will be added to the multiple_choice_list field (which is where you store the data).

The other else if statements from my original post are additional clauses that:

Reset the multiple_choice_list if a user made a mistake and selected a wrong value.
Prevent multiple entries of the same value
Format the choices and separate them by comma

Hope this makes sense, but if not, please let me know and I'll try to explain further. I might share a screen recording, just so you can see how the expected output looks like.

Cheers

Re: Multiple choice option in Field Maps

FlorianTubbesing — Tue, 13 Dec 2022 12:54:43 GMT

Also a big yes from my side!

The Workaround with two fields and Arcade Expression works but it is not handy for the enduser and could not be the solution for our customers.

However i think it is a key feature for many szenarios we had actually and i hope we will see this in the near future.

Re: Multiple choice option in Field Maps

JustinMiller2 — Wed, 14 Dec 2022 23:45:47 GMT

Agreed

This is vital for so many usecases of FieldMaps including environmental surveys.
PLEASE implement this asap.

Re: Multiple choice option in Field Maps

JenniferEvershed1 — Sun, 18 Dec 2022 22:40:40 GMT

Yes would absolutely love to see this! It would make species data collection so much easier.

Just one example: conducting a field assessment with Emergent species, 3x Tree level species, 2 x Shrub level species and 1 x ground level species. I currently have text boxes for each species so that users can enter multiple species in each field (e.g. Tree Level 1: species 1, species 2, species 3. Tree Level 2: species 1, species 2, species 3 etc. )

This means users have to type out the species names each time which is time consuming and error prone. I'd love to use Domains however then I would need to have Tree Level 1, species 1; Tree Level 2, species 2; Tree Level 1, species 3; Tree Level 2, species 1 etc. which is just way too many fields and still restricted by the number of fields I decide to make.

I can see requests for multi select are going back to 2017 can we please please get this into Field Maps? Survey123 just isn't always suitable. In this case, the rest of the survey is best captured in Field Maps so to then set up a separate Survey123, have the users flicking between apps in the field and then have to manage the data separately and bring it all back together at the end is just another series of time sucks.

Multi Select for Field Maps please!!

Re: Multiple choice option in Field Maps

JustinReynolds — Wed, 21 Dec 2022 18:25:39 GMT

I would also like to see a multiple choice option with native support as well.

For those looking for another example of the workaround that uses two fields see below.

Compact Code

// example_multiple_choice_list_workaround var self = $feature.fdt_fill_compact_equip_used; var pEquipCode = $feature.fdt_fill_compact_equip; var pEquipDesc = DomainName($feature, "fdt_fill_compact_equip"); var delimeter; if (IsEmpty(pEquipCode) && IsEmpty(self)){return}; // There is nothing to do... exit early if (pEquipCode == 0){return}; // Clears the list & exits early if (!IsEmpty(pEquipCode)) { IIF(Find(pEquipDesc, self) == -1, pEquipDesc, pEquipDesc = Null); IIF(IsEmpty(self) || IsEmpty(pEquipDesc), delimeter = '', delimeter = ', ') }; return self + delimeter + pEquipDesc

Same code with comments and context

/* example_multiple_choice_list_workaround LOGIC: CORE: Build a comma seperated list based on repeated selections from the compaction equipment field --> faking a multi-select field Clear the current list if 0 is selected *9999 will allow the user to manually edit this field That is handled via an editableExpression ASSIGNED TO: Field -> $feature.fdt_fill_compact_equip_used DOMAIN EXAMPLE: 1 Jumping Jack 2 Impact Roller 3 Grid Roller 4 Sheepsfoot Roller (Vibratory) 0 Clear the List 9999 Manual Entry */ var self = $feature.fdt_fill_compact_equip_used; var pEquipCode = $feature.fdt_fill_compact_equip; var pEquipDesc = DomainName($feature, "fdt_fill_compact_equip"); var delimeter; // var self = 'Jumping Jack'; // TEST VALUE // var self = 'Jumping Jack, Impact Roller'; // TEST VALUE // var pEquipCode = 0; // TEST VALUE // var pEquipDesc = 'Impact Roller'; // TEST VALUE Console('Current Equipment: ' + self); Console('Proposed Equipment: ' + pEquipDesc); if (IsEmpty(pEquipCode) && IsEmpty(self)){return}; // Exits early if (pEquipCode == 0){return}; // Clears the list & exits early if (!IsEmpty(pEquipCode)) { // If pEquipDesc already in self, don't add it again. IIF(Find(pEquipDesc, self) == -1, pEquipDesc, pEquipDesc = Null); // If either self or pEquip is null then a comma is not needed. IIF(IsEmpty(self) || IsEmpty(pEquipDesc), delimeter = '', delimeter = ', ') }; return self + delimeter + pEquipDesc

And as a bonus... setting up the editable expression.

1. Create a visibility expression that will instead be used to control editability (which will enable or disable the calculated expression).

Notice the vis condition below that is not assigned to anything.

The editableExpression (created as if it were a visibleExpression).

/* edt_fdt_fill_compact_equip_used LOGIC: CORE: Enable editing of the fdt_fill_compact_equip_used if compaction equip pick list is set to 9999 => Manual Entry ASSIGNED TO: Field --> $feature.fdt_fill_compact_equip_used */ var valueField = 'fdt_fill_compact_equip'; var field = 'fdt_fill_compact_equip_used'; Console('Enable/Disable Editability on ' + field); var value = $feature[valueField]; // var value = 9999; // TEST VALUE IIF(value == 9999, True, False)

And finally, creating the editableExpression on the field in the web map's JSON using AGOL Assistant.

Re: Multiple choice option in Field Maps

AnthonyJonesRSK — Thu, 23 Feb 2023 17:40:25 GMT

@Woodpecker @JustinReynolds

Just wanted to say thanks to both of you for posting details of your workarounds, that worked a treat. Whilst I'm hoping Esri implement something akin to the Survey123 options soon this will do for now.

It's also made me aware of being able to toggle a fields editability by editing the json and using a conditional arcade expression, which I didn't know you can do. I've had a couple of issues getting mine working but will persevere with it. Cheers

Re: Multiple choice option in Field Maps

DavidSolari — Thu, 23 Feb 2023 19:54:08 GMT

I'd expand this to make multi-choice options a full domain type, that way other parts of the platform can edit multiple choice questions. Bonus points if the choices are stored as bit flags if the backing field is an integer, the Survey123 method of concatenating every choice in the backing field seems wasteful when you can shove 16 choices in a short field.

Re: Multiple choice option in Field Maps

JeffHaney — Thu, 02 Mar 2023 19:32:20 GMT

@JustinReynolds

Thanks for posting your code example and showing the json layer editing. That was a new one for me.

Your code is straight forward, but when trying to implement it I can't get self to retain the prior selection. If I update the record and then edit it will tack on a new selection. Its seemingly referencing the attribute value instead of the text box value. Am I missing something?

Thanks!

Re: Multiple choice option in Field Maps

Brady — Wed, 15 Mar 2023 04:49:57 GMT

@JustinReynolds and any others using this great solution, I couldn't get the clear functionality working with the code using the 0 value even when putting it in the domain.

if (FlwrClrChoice == 0)

but it worked perfectly when I put in 'Clear' as the code and value in the domain and switched it to

if (FlwrClrChoice == "Clear")

I haven't implemented the visibility component yet but it's all working great.

Re: Multiple choice option in Field Maps

JustinReynolds — Fri, 17 Mar 2023 15:56:12 GMT

For those using AGOL, you can now natively author this solution in the Field Maps Designer. This is because you can now author editability constraints. For those in Enterprise, hopefully we will see that in 11.1.

Re: Multiple choice option in Field Maps

JustinReynolds — Fri, 17 Mar 2023 15:57:51 GMT

@JeffHaney It is hard to say without seeing the code. You can DM me if you don't want to post it here and I can take a look and offer up some advice.