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.
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.
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).
@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.
@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.
@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.
Thanks for considering.
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.
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:
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.
@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
@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
@Anonymous User Hi Aaron i'm also keen for any updates on this topic!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.