idea Allow Select Multiple Questions in Field Maps in ArcGIS Field Maps Ideas

Allow Select Multiple Questions in Field Maps

RogerCleaves1 — Tue, 23 Feb 2021 21:25:04 GMT

We would love to be able to implement select multiple type questions in Field Maps. We currently have a use case where field staff need to select multiple types of waste found on a site and record contextual information for each one.

This is the current design in Survey123, but we would love to migrate this all into one single app instead of using Collector for visibility in the field, and Survey for collecting the data.

Re: Allow Select Multiple Questions in Field Maps

erica_poisson — Mon, 01 Mar 2021 14:12:18 GMT

I would love to see this implemented in Field Maps. I do not think it would in any way replace Survey123 (there are just so many other things that make that fantastic), but it would be great to help streamline certain workflows if we could just use one platform (Field Maps) to collect data, like Roger mentions.

Re: Allow Select Multiple Questions in Field Maps

BenSmith6 — Fri, 14 May 2021 15:07:22 GMT

This is desperately needed in Field Maps, Survey123 (as Erica mentioned) does so much more that I don't think it would impact it's use at all

Re: Allow Select Multiple Questions in Field Maps

CinthiaEichhorn — Mon, 31 May 2021 03:35:29 GMT

This is NEEDED. Many wildlife biology surveys are map centric, and have a need for choosing multiple answers. For example: the condition of a vhf transmitter that has been found.

The vhf transmitter's condition can be: chewed, curled, torn apart, bite marks, or a combination of these four options. There are ways to create this question/response to fit into Field Maps, but a select multiple type would be the most intuitive for the field users.

Moreover, if there was a select multiple type in field maps, it would be more efficient to implement than the current Collector calling a S123 form combo.

Re: Allow Select Multiple Questions in Field Maps

SimoneMoretti_MRC — Mon, 31 May 2021 11:07:40 GMT

an collection . Hoping available

Re: Allow Select Multiple Questions in Field Maps

MatthewGuilliatt — Wed, 01 Sep 2021 17:30:32 GMT

This is also vital for my data collection.

Survey123 is great, but it is weak in displaying reference layers, fieldmaps is great for displaying reference data, but we can't capture the information we need to.

Re: Allow Select Multiple Questions in Field Maps

SSMGroup — Thu, 30 Dec 2021 12:09:13 GMT

This should be top priority!!

Along with Choice Filters.

I cannot make the switch to field maps until these functionalities are available.

@DougBrowning Maybe you can help get this post suggestion noticed by Esri. This would be a wonderful addition to Field Maps, and it's really needed. I'd love for my users to be able to stay within one app for the workflows I create.

Re: Allow Select Multiple Questions in Field Maps

Anonymous User — Tue, 04 Jan 2022 18:15:01 GMT

We're well aware of this request, it's one of the most requested form features (along with calculated values and contingent values). It's not something we're planning to implement in the next quarter but perhaps later in 2022 we could. Here's some questions we have for you that might help us:

Survey123 implements this as a comma delimited list of values stored in a string field. This can make it difficult to re-use in other areas of ArcGIS. For those of you who use Survey123:

How do you use the captured data for these fields?

Do you show the layers in other apps/maps besides Survey123?
Do you use hidden fields & calculations to split the choices into separate fields?
Do you use Arcade in Pop-ups and Dashboards to format the data?

Would you expect to be able to create a multiple choice element for existing fields?

If so, do those fields have existing coded value domains? Are they string fields or integer fields?

Would it be beneficial to have a multiple choice UI/UX that stores each choice in a separate "boolean" field instead of a comma delimited list?
How many choices per question are anticipated?
Would you need to add or remove choices over time?

If so, should that affect previously collected data?
Would you need to deprecate choices over time?

Would you need to edit an existing choice name/values?

If so, should that affect previously collected data?

Do the choices needs any additional information displayed with them, like a description? Or is the value/name enough?

If so, can you provide a specific example?

Re: Allow Select Multiple Questions in Field Maps

RogerCleaves1 — Tue, 04 Jan 2022 18:34:00 GMT

@Anonymous User Here's the responses to your questions! I'd be more than happy to talk through our specific use cases.

Survey123 implements this as a comma delimited list of values stored in a string field. This can make it difficult to re-use in other areas of ArcGIS. For those of you who use Survey123:
- Do you show the layers in other apps/maps besides Survey123?
- We use a view of the data in some internal and external dashboards
- Do you use hidden fields & calculations to split the choices into separate fields?
- Not right now, but have experimented with that as an option to parse the data
- Do you use Arcade in Pop-ups and Dashboards to format the data?
- Yes, we use Arcade to parse the data based on the types selected in the select multiple field

How do you use the captured data for these fields?
We use the data to provide summaries of which type of HHW or Asbestos is collected at each facility.

Would you expect to be able to create a multiple choice element for existing fields?
No

If so, do those fields have existing coded value domains? Are they string fields or integer fields?

Would it be beneficial to have a multiple choice UI/UX that stores each choice in a separate "boolean" field instead of a comma delimited list?
That would make it easier to work with the data for visualizations and other data exploration
How many choices per question are anticipated?
For this use-case, at least 20 options would work
Would you need to add or remove choices over time?
Not necessarily, but it would be nice to have that option

If so, should that affect previously collected data?
No
Would you need to deprecate choices over time?
No

Would you need to edit an existing choice name/values?
No

If so, should that affect previously collected data?
No

Do the choices needs any additional information displayed with them, like a description? Or is the value/name enough?
Value/Name should be good enough for us

If so, can you provide a specific example?

Re: Allow Select Multiple Questions in Field Maps

erica_poisson — Wed, 05 Jan 2022 13:39:22 GMT

@Anonymous User -

Hoping to chime in here with some answers to your questions as this is something we'd also love to see implemented in Field Maps. If this was added, we'd be able to simplify some field workflows by removing the Survey123 component (which is used if we need to select multiple values).

Survey123 implements this as a comma delimited list of values stored in a string field. This can make it difficult to re-use in other areas of ArcGIS. For those of you who use Survey123:

How do you use the captured data for these fields?

Do you show the layers in other apps/maps besides Survey123?
- Yes - we generally display collected data in Dashboards.

Do you use hidden fields & calculations to split the choices into separate fields?
- No - we store the data as comma delimited and then work with it later using Arcade Data Expressions or something like R.
Do you use Arcade in Pop-ups and Dashboards to format the data?
- Yes - we use Data Expressions in Dashboards to break the data out for charts.

Would you expect to be able to create a multiple choice element for existing fields?

Primarily this would be used to migrate existing (simple) workflows from Survey123 to Field Maps. We have existing domain values assigned already and would like to just "check off" a select multiple option to allow for multiple choices to be selected. Similar to the experience when building a Survey123 form in Connect "on top" of an existing feature layer.
If so, do those fields have existing coded value domains? Are they string fields or integer fields?
- Yes to existing coded value domains - both string and integer fields, however string is much more common.

Would it be beneficial to have a multiple choice UI/UX that stores each choice in a separate "boolean" field instead of a comma delimited list?
- I'd be interested to see how this would affect schema design. It sounds nice, but with the capabilities of Data Expressions, I am unsure if I'd give a hard and fast "yes" here without knowing more about how the schema is affected for existing data layers.
How many choices per question are anticipated?
- I'd agree with @RogerCleaves1 that ~20 choices would be adequate when thinking of my existing workflows that I'd like to migrate.
Would you need to add or remove choices over time?

Potentially.
If so, should that affect previously collected data?
- No - if a choice is added or removed, all existing data with that value should not be changed.
Would you need to deprecate choices over time?
- Potentially - same response as above.

Would you need to edit an existing choice name/values?

Ideally not, but it is always possible.
If so, should that affect previously collected data?
- It would be nice, but this can also be dealt with via Pro.

Do the choices needs any additional information displayed with them, like a description? Or is the value/name enough?

It would be ideal, in my opinion, to have a similar set up to Survey123 where you have the stored code and the label that is shown to the user in the application.
If so, can you provide a specific example?
- We have coded values for our subbasins - 5 = Ball Brook. We don't want a list of numbers to show up for users, we want the list of labels that correspond. Another example would be for stream codes - the description is much more useful for field staff.

Re: Allow Select Multiple Questions in Field Maps

KyleLandon — Wed, 05 Jan 2022 16:56:19 GMT

Survey123 implements this as a comma delimited list of values stored in a string field. This can make it difficult to re-use in other areas of ArcGIS. For those of you who use Survey123:

How do you use the captured data for these fields?

Do you show the layers in other apps/maps besides Survey123?
Do you use hidden fields & calculations to split the choices into separate fields?
Do you use Arcade in Pop-ups and Dashboards to format the data?

Haven't used Survey123, doesn't meet needs.

Would you expect to be able to create a multiple choice element for existing fields?

If so, do those fields have existing coded value domains? Are they string fields or integer fields?
Since it's not available as a way to collect data, I haven't made fields to do this. I think coded value domains would be most fail-safe/elegant. A good way to capture "Other" would be nice. We should be able to have a conditionally visible field to capture it.

Would it be beneficial to have a multiple choice UI/UX that stores each choice in a separate "boolean" field instead of a comma delimited list?
- I can see how this may be helpful, probably not as big a difference maker if using coded domains
How many choices per question are anticipated?
- Maybe a dozen or so at most
Would you need to add or remove choices over time?

Probably.
If so, should that affect previously collected data?
- I think it's not unreasonable to say we'd have to script repairs or fixes as needed.
Would you need to deprecate choices over time?

Would you need to edit an existing choice name/values?

Most likely
If so, should that affect previously collected data?
- yes, but I'd think one could script the change or manually fix.

Do the choices needs any additional information displayed with them, like a description? Or is the value/name enough?

Value/Name is fine
If so, can you provide a specific example?

Re: Allow Select Multiple Questions in Field Maps

Anonymous User — Wed, 05 Jan 2022 20:43:04 GMT

@erica_poisson

We have existing domain values assigned already and would like to just "check off" a select multiple option to allow for multiple choices to be selected. Similar to the experience when building a Survey123 form in Connect "on top" of an existing feature layer.

@KyleLandon

I think coded value domains would be most fail-safe/elegant. A good way to capture "Other" would be nice. We should be able to have a conditionally visible field to capture it.

So is it okay that the stored value is comma separated and does not match a coded value? For example consider a string field that stores types of fruit with coded values of "Apples", "Oranges", and "Strawberries". If the user selects Apples and Oranges. The resulting value will be "Apples,Oranges" which does not match a coded value. Some people might consider this invalid/bad data. For what it's worth, this what Survey123 does today when using an existing layer.

In the case where the field doesn't have a coded value domain, it doesn't really matter but then the options need to be defined in the form (not in the layer).

Re: Allow Select Multiple Questions in Field Maps

erica_poisson — Thu, 06 Jan 2022 13:22:42 GMT

@Anonymous User - I am so used to the way Survey123 deals with this that it is really not an issue to me anymore as Survey123 is my agencies primary method of field data collection. That being said...anything that can be done to improve the experience in Field Maps would be welcome. I would only wonder for those workflows that might be migrated from Survey123 to Field Maps (if select multiple became available and the stored value method was different from how Survey123 does it), how would the data be affected? It seems content managers would need to do some work to fix things in the table.

Re: Allow Select Multiple Questions in Field Maps

Erwinvan_Veen1 — Tue, 22 Feb 2022 14:54:03 GMT

@Anonymous User Thank you for keeping track of this much-requested feature.

Although I understand it strictly may not comply with domains, it is easy to use LIKE '%...%' types of filters to still work well with the data. Either inside or outside of ArcGIS software. When needed, we can easily explode the attribute should that be needed.

Don't get me wrong, although you were asking many relevant questions earlier, it feels a bit odd. For example, how many choices are expected feels like a possible limitation where it shouldn't be one. And whether or not the data is to be able to edit again isn't a question: it is a clear must for me. As an outsider, it would seem similar functions like Javascript string 'split' and 'join' functions should be available and not too different from Survey123. We see Esri developing many different products, apps, et cetara in which some functions are available or work in a certain way but do not appear at all or work differently in others. To me it feels unproffessional to ask end-users to switch apps all the time. Some coherency would me much appreciated. I do understand it is easy for us to ask and not quite as easy to develop. So please, do not take my comment the wrong way.

I sincerely hope this idea is implemented in the foreseeable future.

Re: Allow Select Multiple Questions in Field Maps

BrendanFordDC — Thu, 24 Feb 2022 19:13:38 GMT

@Anonymous User

Also chiming in. Overall for the project I am working on this would likely keep me from having to also integrate Survey123. I'll probably still work around it but having this functionality would shorten the time it takes staff to survey an asset.

Survey123 implements this as a comma delimited list of values stored in a string field. This can make it difficult to re-use in other areas of ArcGIS. For those of you who use Survey123:
- Do you show the layers in other apps/maps besides Survey123?
  - Yes - same as Erica we display collected data in Dashboards.
- Do you use hidden fields & calculations to split the choices into separate fields?
  - No we can query the data using a qualifier.
- Do you use Arcade in Pop-ups and Dashboards to format the data?
  - Yes some

How do you use the captured data for these fields?

Would you expect to be able to create a multiple choice element for existing fields?

Using Erica's answer: Primarily this would be used to migrate existing (simple) workflows from Survey123 to Field Maps. We have existing domain values assigned already and would like to just "check off" a select multiple option to allow for multiple choices to be selected. Similar to the experience when building a Survey123 form in Connect "on top" of an existing feature layer.
If so, do those fields have existing coded value domains? Are they string fields or integer fields?
- String fields. A small number of available values.

Would it be beneficial to have a multiple choice UI/UX that stores each choice in a separate "boolean" field instead of a comma delimited list?
- Yes. Having the data in their own fields is fine it is more about getting the data on the form in a fast efficient way.
How many choices per question are anticipated?
- I'll agree with my colleagues that 20 is a decent number. If you had to go much beyond that the data should probably be broken down into different questions.
Would you need to add or remove choices over time?

More likely to add than to remove but would be nice.
If so, should that affect previously collected data?
- No
Would you need to deprecate choices over time?
- Maybe.

Would you need to edit an existing choice name/values?

Not if we set our questions up right in the beginning.
If so, should that affect previously collected data?
- No. As pointed out this data could be edited in Pro

Do the choices needs any additional information displayed with them, like a description? Or is the value/name enough?

The value should be enough.
If so, can you provide a specific example.

Thanks for considering.

Re: Allow Select Multiple Questions in Field Maps

cbp-geus — Wed, 06 Apr 2022 15:05:01 GMT

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

We are hoping to use this app for our geologist field work, but we need to be able to select one or more vital information in the field for attributes such as lithology description, mineralogy composition, fossil registration etc from one data point collection.

Re: Allow Select Multiple Questions in Field Maps

andreoudi — Mon, 16 May 2022 14:51:35 GMT

Survey123 implements this as a comma delimited list of values stored in a string field. This can make it difficult to re-use in other areas of ArcGIS. For those of you who use Survey123:

How do you use the captured data for these fields?

Do you show the layers in other apps/maps besides Survey123?

Yes - we generally display collected data in Storymaps and Dashboards.

Do you use hidden fields & calculations to split the choices into separate fields?

We do this if there is a need to present the data in a chart. But we also use the comma delimited data and we present it in popups with the help av arcade.

Do you use Arcade in Pop-ups and Dashboards to format the data?

Yes

Would you expect to be able to create a multiple choice element for existing fields?

That would be great but it is not neseccary.

If so, do those fields have existing coded value domains? Are they string fields or integer fields?

I have only worked with String vaues in survey123 but it should be possible with both.

Would it be beneficial to have a multiple choice UI/UX that stores each choice in a separate "boolean" field instead of a comma delimited list?

Yes, I think that this would be very nice

How many choices per question are anticipated?

I personaly haven’t had the need for many choices but around 10 would be nice

Would you need to add or remove choices over time?

There is always the possibility that this would be necessary at one point.

If so, should that affect previously collected data?

I don’t think that should affect the previous data.

Would you need to deprecate choices over time?

Same as above.

Would you need to edit an existing choice name/values?

You should be able to do this.

If so, should that affect previously collected data?

You can always edit data in ArcGIS Pro so I don’t hink that this is an issue.

Do the choices needs any additional information displayed with them, like a description? Or is the value/name enough?

The label would be enough in this case.

Re: Allow Select Multiple Questions in Field Maps

SolanaFoo2 — Mon, 19 Sep 2022 19:21:27 GMT

Yes PLEASE!! Arcade has opened up new possibilities for us in Field Maps and we are excited to use it in SmartForms. Please implement this so we have a fully robust solution there.

Re: Allow Select Multiple Questions in Field Maps

HarmondSantos1 — Tue, 29 Nov 2022 23:54:15 GMT

@Anonymous User, here's some more answers to the questions you posted. Hope this helps.

We've been using Survey123 a lot with Enterprise, utilising our SDE server to publish services to be used as submission URL. One thing we find lacking here is the ability to edit those select multiple questions. We usually provide a web app with Smart Editor for the people in the office to review or the custom table edit tool and make edits to the submissions of the field workers. People find it easier to edit data in a tabular form or a web app rather than go through the Survey123 form again

Survey123 implements this as a comma delimited list of values stored in a string field. This can make it difficult to re-use in other areas of ArcGIS. For those of you who use Survey123:

How do you use the captured data for these fields?

Do you show the layers in other apps/maps besides Survey123? Yes, we display them in Dashboards and Web Apps, with the capability to edit/update information.
Do you use hidden fields & calculations to split the choices into separate fields? No, we stick with the comma separated values and make it readable using Arcade expressions.
Do you use Arcade in Pop-ups and Dashboards to format the data? Yes, we use arcade to make the comma separated values more readable to users.

Would you expect to be able to create a multiple choice element for existing fields?

If so, do those fields have existing coded value domains? Are they string fields or integer fields? Not necessary for us - probably something nice to have. With Survey123, I only use strings for select multiple questions.

Would it be beneficial to have a multiple choice UI/UX that stores each choice in a separate "boolean" field instead of a comma delimited list? It would be good to have this option - easier to display in dashboards and get more insight to the collected data easily.
How many choices per question are anticipated? Project I'm working on now has 15 choices
Would you need to add or remove choices over time? Yes, there's always that possibility.

If so, should that affect previously collected data? No, don't think it should affect the existing data.
Would you need to deprecate choices over time? I don't think so. I think that the choice list would just grow.

Would you need to edit an existing choice name/values? Yes

If so, should that affect previously collected data? Yes, but as mentioned above, we can always edit the data on ArcGIS Pro

Do the choices needs any additional information displayed with them, like a description? Or is the value/name enough? Value/name should be enough

If so, can you provide a specific example?

Re: Allow Select Multiple Questions in Field Maps

JustinMiller2 — Wed, 14 Dec 2022 23:11:23 GMT

@Anonymous User Hi Aaron, is there any update on this? Nearing the end of 2022, and I believe it is still a super important feature for many use cases of FieldMaps.

Cheers