idea Multiple Coded Values per Record in ArcGIS Pro Ideas

Multiple coded value for a domain

EmilianoTondi — Thu, 25 Aug 2022 22:40:02 GMT

I think is needed to permit to choose form multiple coded values in a Domain. Often the user just wants to add more than one value present in the list of the Domain; now you have to add more fileds to store more info from the same domain. Instead I think it is necessary to able the geodatabase to insert more than a coded value from the same Domain as it happens in Access (from 2007 version).

Multiple Coded Values per Record

SimonTrinder1 — Wed, 03 Apr 2024 01:50:07 GMT

I would like the ability to choose multiple values from a Domain and assign to a field. ie. Apples, pear, Oranges

Field name = Contents
Domain Name = Fruit
Coded Values =Apples(A), Orange (O), Pears(P), Strawberry(S).

I would like to be ableto choose one or a combination of the values Apples or Apples & Oranges or Apples & Oranges & Pears etc.

So instead of a drop down, when editing the field, there is a check list where I could choose mutiple values.

Re: Multiple Coded Values per Record

CarmellaBurdi1 — Thu, 23 Jul 2015 14:19:30 GMT

If this hasn't been created yet, especially with the concept behind GeoForms, this would be a very valuable resource to have.

Re: Multiple Coded Values per Record

KelseyBoyd — Fri, 11 Dec 2015 15:32:54 GMT

This would be incredibly useful to our organization. I am trying to figure out work arounds for this, but it is resulting in very long collector forms, increased time to fill in forms, and/or loss of consistency. If ESRI doesn't add this function, we may have to use a different product.

Re: Multiple Coded Values per Record

ChrisMathers — Wed, 06 Apr 2016 16:41:21 GMT

The problem here is the the form mirrors the database functionality. The goal of a domain is to standardize input into a field and this would do the opposite. Database opperations would be slowed because to search accurately on that field you would have to parse the list contained in each record.

Re: Multiple Coded Values per Record

SamJenkins2 — Fri, 06 Jan 2017 16:38:05 GMT

Chris,

I like the functionality of this idea, but was concerned about searching data afterward as well. Could your hesitancy be persuaded if the domain was interpreting a bitgate?

Cheers

Sam

Re: Multiple Coded Values per Record

AndrewZimba — Fri, 15 Sep 2017 14:09:08 GMT

Not exactly - If in the example the OP posed the user selected that all 4 types apply the stored value could be a delimited string - A; O; P; S and searches could be done using Like instead of =

Re: Multiple Coded Values per Record

JohnDye2 — Tue, 01 May 2018 16:12:59 GMT

I like the idea but the biggest problem I see with it is that the having a multi-value selection has development implications across the entire ArcGIS Platform. Esri would need to come up with a well known multi-value selection syntax, say semi-colon delimited as demonstrated by Andrew Zimba‌ and the somehow reserve that syntax across the platform and ensure that all applications and solutions had built-in logic to detect, parse and visualize that data in the solution UI.

That means dev effort for Pro, Online, Web App Builder, OpsDB, Workforce, Collector, GeoPlanner...the list goes on and on. Multi-value selections are useful, I agree. It's just that this while seemingly a small development effort has some pretty massive implications when you scale it out to the entire platform.

Fwiw, Survey123 already does multi-value selection but perhaps there's a standard defined there and all of the other Esri App teams could just on board with that, but even so - this is no small ask.

Re: Multiple Coded Values per Record

ChrisMathers1 — Tue, 01 May 2018 18:46:46 GMT

What if it was a NoSQL database being used? With everything essentially as JSON objects you can make the field an array and the chosen values can be objects within it. The query as a concept changes a bit as does storage in general but it would work. They would need to write an ODM to run in place of the normal ORM for relational databases though and like you said that's a system wide undertaking. esri products don't do much with NoSQL databases at the moment but I can see that changing in the future especially with the shift towards big data analytics. They already use MongoDB with Monitor but that's not a core spatial product so it only tangentially applies. Mongo uses GeoJSON as its spatial type so hypothetically you could run the esri JS API off of it with changes to the query back end.

Multiple Selection option should be available to while designing geodatabase with Dropdown option

TikaAdhikari — Tue, 16 Apr 2024 16:16:40 GMT

Dear Developer Team,

We have single choice is available now in the geodatabase. Do we consider multiple selection options ? Currently multiple selection option is available for Survey123. I would like to publish feature service with multiple selection option. For example, I want to understand the health behavior of people in detail manner in geospatial perspective. In the database is it is the selection of fruits( but in the survey what kinds of fruits do you eat). The same person may eat apple, orange and banana or all of them in the same day which cannot capture in current design in efficient design technique. Therefore this request is important to have consistence integration from database to Survey123 to capture real world data in a realistic manner.

Let me know if you want more clarification.

With Best Regards,

Tika

Re: Multiple Selection option should be available to while designing geodatabase with Dropdown option

KoryKramer — Tue, 17 Nov 2020 20:35:06 GMT

From the description, this sounds like the same request as Create a new Hosted Feature Service Domain Type: c... - GeoNet, The Esri Community .

Tika Adhikari‌ could you read through that idea and let us know if that is what you are asking for?

Thank you!

Re: Multiple Selection option should be available to while designing geodatabase with Dropdown option

TikaAdhikari — Mon, 09 Nov 2020 19:35:32 GMT

I want multiselect option in the database. For example, example under the fruit attributes, I would like to include all fruits I eat every day. Same as in your example, money/payment is the attribute, I would like to pay with credit card and debit card with for 100 bill.

Re: Multiple Selection option should be available to while designing geodatabase with Dropdown option

TikaAdhikari — Mon, 09 Nov 2020 19:37:54 GMT

It is not and it is entirely different and it is not hosted feature service.

Re: Multiple Selection option should be available to while designing geodatabase with Dropdown option

KoryKramer — Mon, 09 Nov 2020 20:16:57 GMT

Thank you for the response. So from a coded value domain, you would like to be able to select multiple, correct?

And you're not working with a hosted feature service. You're working in a geodatabase, correct?

Re: Multiple Selection option should be available to while designing geodatabase with Dropdown option

TikaAdhikari — Mon, 09 Nov 2020 20:19:22 GMT

Yes, it is not for hosted feature service to be clarify in a much better way.

Re: Multiple Selection option should be available to while designing geodatabase with Dropdown option

TikaAdhikari — Mon, 09 Nov 2020 20:20:50 GMT

The issue is enterprise or file geodatabase if I have to separate the domain of the problem. But it has other applications value

Re: Multiple Coded Values per Record

Bud — Thu, 08 Jun 2023 16:51:49 GMT

Interesting idea. The underlying data could be stored in a related table (1:M). But the multiple values could be chosen and displayed in the main attribute table/field. That would be easier to view & edit when compared with navigating to a related table.

Alternatively, the multiple values could be stored in an XML column, which would be queryable via SQL in enterprise geodatabases (not sure about mobile geodatabases).

There are probably other ways to do it, such as a comma-delimited field, as mentioned in a comment above. The values could be automatically sorted in alphabetical order upon entry.

Enter multiple domain values in one field

KimberlyWinter — Fri, 19 Dec 2025 16:36:43 GMT

Can we allow mutliple domain values in one field i.e. often we have in forestry multiple different species in one subcompartment. It is impossible to add all of these different combinations as part of a domain but we require data standardisation.

If you could choose SS / LP/ MB with 'SS' 'LP' and 'MB' all as separate domain values it would ensure the data is standardised without having to add every combination within the domain.

Re: Enter multiple domain values in one field

HollyTorpey_LSA — Mon, 08 Dec 2025 17:12:42 GMT

I don't know if it would make sense in your workflow, but you might want to consider using a Survey123 form as your data entry mechanism. Survey123 forms allow multi-select questions and then store the response as comma separated values in a single field.

Re: Enter multiple domain values in one field

troyf_PTC — Tue, 09 Dec 2025 16:10:21 GMT

And following along with @HollyTorpey_LSA's point, you can build similar functionality within Forms via @Woodpecker 's solution in this idea page Multiple choice option in Field Maps - Esri Community

I have tested it and it seems to work fairly well in trying to convert some of my Survey123 surveys into Smart Forms (in some cases the clearing values might take a minute or so to recalculate to blank with the way I had set it up).