Filter by more than one domain at a time in an attribute set in Field Maps

[L77]

Use case:

we have summer interns inventorying all of our county survey monuments.

If they mark a monument as "Behind a Fence" or "Private Property Permission Needed", then our surveyors will have to inventory those monuments.

The surveyors would like to filter to see both of those locations on the map at once, instead of having to filter one status at a time.

It would be nice if these were checkboxes and we could filter by as many domains as we would like, instead of just one domain.

[Fabian_Shenk]

Arcade should be the way to go to filter based on status without having to click a box or set within the map. The analyst should be able to set your map up with a statement to have these types of status at the ready, or create a surveyor map "viewer"

[L77]

@Fabian_Shenk I am the analyst. I want my users to be able to filter on any of the data that they enter into a feature class that is editable in field maps.

They should be able to check boxes for any domain that has standard options in the drop down menu.

I shouldn't have to do extra work to configure their apps, and they should be able to filter on any of their inputs.

In web app builder and in the new instant apps users can filter by any attribute that has a domain. Field maps should have the same capabilities. 

[Fabian_Shenk]

Hello L77 - certainly did not mean anything with calling on the analyst. I was pointing to a simple arcade statement that might make production quicker.

I certainly understand about the workload and not causing you any additional work.

Maybe a script could be created to run automatically to filter to a workflow for the surveyors. I was just thinking in regards to efficiency and quick thinking.

Just some thoughts - I know it can be frustrating to see some options in other applications vs. what we may have in front of us. 

Thank you for replying.

[L77]

@Fabian_Shenk I'm not offended and didn't mean to sound harsh. 

That is the main thing for me, seeing the features in other tools and needing them in the field.

For all of our field staff we have instant app they can use at their desks to edit, search and filter. Then in the field they are doing the same thing with field maps. So they are used to having the ability to filter at their desks.

It gets complicated because some of the data they have can't sync offline, so I have a  map viewer template with an instant app that includes all of the data, then another map viewer for field maps that is identical and doesn't include the data that can't sync offline. I have to configure everything twice, so by the time I have their field maps app setup, I like to click the checkbox so they can filter on anything in their app.