nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can you limit the drop down list of domain values displayed in one field based on a value provided in a previous field using Arcade for Field Maps?

Anonymous User

I have a dataset being used where a crew member will determine an Observation Code based on the conditions they're seeing in the field. Once they've selected the Observation Code they have to select a 'Recommended Follow Up Action' in a separate field. Currently, they have to select from the entire list of possible 'Recommended Follow Up' values that are in the Domain but ideally I'd like only the choices relevant to the selected Observation Code to be shown. Is this possible?

I've set something similar up for this in S123 but we're migrating the whole process to Field Maps.

@Anonymous User The expressions you shared in another thread in response to user Valven were really helpful for me, would you have any ideas?

Thanks for any and all suggestions!

Find more posts tagged with

Accepted answers

Anonymous User

Currently this is not possible using Arcade. Field Maps (and Collector) use the domains defined in the fields, types, or subtypes. There is an on-going effort with hosted feature services, runtime, and the apps to support contingent values that are published from ArcGIS Pro.

One option that might work for you (if you only need one field to control other fields) would be to define sub-types using the Observation Code field as the sub-type field. You could then define a different set of domains for each sub-type. Sub-types can be authored in ArcGIS Pro and are supported in Field maps today.

All comments

Anonymous User

Looking forward to when we can bring contingent values over from Pro, until then I'll look into the sub-type work flow you suggest. Thanks for the speedy reply!

LeanneTough

Do you have any documentation on this Aaron? I don't entirely understand how this would solve the problem.

Anonymous User

@LeanneTough Subtypes can have different coded values for each type of feature.

For example, say you are collecting fruit tree information. If the subtype field is "tree_type" and options are "Apple" and "Cherry", then for the "fruit_type" field you could have options of "Honey Crisp" and "Cortland" for apple trees, and have options of "Black Tartarian" and "Sweet" for cherry trees.

The main limitation is that this only works when a single field ("tree_type") is controlling the domains.

NurullahAdıgüzel

In the current version, is it possible to restrict the domain using Arcade on Field maps?

Anonymous User

@NurullahAdıgüzelThis is not possible in the released version. The Field Maps team is actively adding support for contingent values - stay tuned.

GaryChristensen1

I've created a group of attributes that I only want to display for certain subtypes - subtypes related to water utilities. So this is what I tried:

var sublist
sublist = Subtypes($feature)

IndexOf(["Water Connection", "Water Junction Fitting", "Water Pressure Valve", "Water Service Valve", "Water System Valve"], sublist) >= 0

That didn't work, so it seems like I should be querying the Subtype Code where "Subtype Code in (6, 13, 14, 17, 22) . Any help with this would be appreciated.

Kevin_MacLeod

did they ever add this?

Also-- I am wondering if they plan to add an even simpler idea, which is different. Ability to simply filter values, in Field Maps Designer. No contingent value field. Just a simple filter on the choice list, for a field. Reason? Let's say I have a Material domain for a Material field. On Sewer Pipes I want 10 choices. The same domain for Manholes, I just want 4 choices. Yes, I could have a field in both layers, saying whether it's a pipe or a manhole. But that's kind of an unneeded field and with utilities we already have so many fields, I don't want a field that simply states what the layer is. We know what the layer is, it's a pipe. Or manhole. Contingent Values are super cool, and it's fantastic they're coming (came?) to Field Maps. Field Maps Designer is wonderful. Like Story Maps and WebApp Builder teams... The Field Apps team "gets it". They are hitting home run after home run, great work. I absolutely love Field Maps Designer, it's what we've always needed. Ability to filter a domain for a field, so we can have different choices from the domain in different layers, would be wonderful. If no one has suggested this I'll make an Idea.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.