Multiple choice option in Field Maps

[ZoevdbAT]

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? 

[SarahSaint-Ruth]

You can try this out soon in our Early Adopter Program - we would love to hear your feedback!

https://earlyadopter.esri.com/key/ArcGISFieldMaps

See what else is planned for the June release:

https://community.esri.com/t5/arcgis-field-maps-blog/arcgis-field-maps-early-adopter-program-is-now/...

[KatieQuantrell]

Hi, 

I was really excited to see that a multiple choice option was being included for Field Maps firms in this June release. 

However I have just gone to try and change some of my fields in a form from their current radio button input type to the new multiple choice input type but its not given as an option?

I can see you can add new multiple choice elements to a form (as long as its not a view layer).

But was assuming we would also be able to set existing field to use this input type. 

Is this as expected or am I missing something?

Any help/advise would be much appreciated. 

Many thanks

[AnthonyJonesRSK]

Hi @KatieQuantrell, does your field have a domain configured? The multi-choice field uses comma separated lists so will only work on text fields without a domain (a bit like how S123 works). 

[AlfredBaldenweck]

That seems like a deficiency in implementation tbh.

[Jeremy_Z]

Agreed Fred, considering the work around for this for years was domain based and it stored the selections as a CSV in a text field, I figured they were using that same process.

[ChristopherBowering]

It does seem counterintuitive from a design, management and efficiency standpoint to be required to move away from domains to make the multiple choice functionality work as described.  Just because you may want to use multiple choice within the Field Maps form doesn't mean the source field isn't used in desktop editing - or other apps - where domains would continue to be integral to the workflow.  Are we expected to maintain separate, identical fields depending on the usage?

[KatieQuantrell]

Thanks @AnthonyJonesRSK  I've deleted the domain list from the two fields that I wanted to convert to multiple choice, and one of the field now gives me the multiple choice option (see 1st image below). But the other field doesn't (2nd image below)? as far as I can tell both fields are set up in the same way. Do you have any ideas on why this would be?

Many thanks.

[AnthonyJonesRSK]

Hi @KatieQuantrell,

I confess I've only dabbled with the new functionality so haven't looked into all its quirks just yet. The documentation is here and there is a line in there that says "If your field has a list of values in it, is part of a contingent value field group, is a primary or foreign key in a relationship, or is a system field, you cannot change it to a multiple choice input type.". I don't know if any of that applies to your second field?