Contingent Value/Cascading Select/Allowed Domain Values

ChristopherDawe — Fri, 29 Aug 2025 15:53:29 GMT

I am trying to emulate the behavior of "Cascading Selects" in Survey 123 but for use in field maps.

I have an existing survey that users have been working with for some time that has cascading selects . I also want the ability to edit and add features via Field maps (particularly so people don't have to cycle through multiple repeats to get to the correct feature) but am struggling with how to implement this.

I am aware that field maps can provide this functionality if contingent values are set up in ArcGSI Pro and the feature layer is published from there, but i already have the hosted feature layer that was generated by publishing the Survey 123. The topic seems to have been asked here https://community.esri.com/t5/arcgis-field-maps-questions/adding-contingent-values-to-hosted-feature-layer/td-p/1185668 as well but no easy solution seems available.

Having also used Sweet for ArcGIS for other applications, which does not honour contingent values, the method in there is to use a decode function in arcade to populate the allowed values using the script below, however when entering this into the calculated expression function in field maps form designer, its says that its invalid.

Is there a method of limiting domain values based on previous answers (ie contingent values/cascading selects) through arcade scripting in Field maps.

It's a little frustrating that of the three esri field data collection apps (field maps, Survey123, Sweet) that there isnt a compatible method across all three

Re: Contingent Value/Cascading Select/Allowed Domain Values

ClayDonaldsonSWCA — Fri, 29 Aug 2025 15:59:11 GMT

Agreed - the lack of consistency is a pain. The hacky workaround I use is something like this:

species_type = ['flora','fauna']
species_flora = [<list of flora species>] | conditionally visible
species_fauna = [<list of fauna species>] conditionally visible
species_value = hidden field that pulls either `species_flora` or `species_fauna`

species_value holds the actual choice in a single spot, so I don't have to look for multiple fields in reports/symbology/etc.

I have tried contingent values in the past - but they are a total pain to update post-publish.

topic Contingent Value/Cascading Select/Allowed Domain Values in ArcGIS Field Maps Questions

Contingent Value/Cascading Select/Allowed Domain Values

Re: Contingent Value/Cascading Select/Allowed Domain Values