Is it possible to use a group filter where you may be able to choose a display field that differs from the field that is actually doing the filtering?
Example: Say I wanted to have a group filter applied to State Polygons, County Polygons, and City Points.
States has a field with Full Name and Abbreviation
Counties has only Abbreviation
City has only Abbreviation
I would like to use State as the main layer and have a list of unique Full State names, but apply the group filter to the abbreviation field, since that is the field that is common in all feature layers.
Is that possible?
Solved! Go to Solution.
You could use the "Unique (predefined)" option under "Select source type" (in your screenshot). This would entail adding all the abbreviations one-by-one (as codes) along with their full names (display values). There is no way to designate a field simply to display but not filter on--there has to be a value connection, it can't just be a record connection.
Hi @AndrewBowne,
Just for clarification purposes. Are wanting a group filter in an application, a map, or some other interactable source? Without knowing which application you are referring to it is difficult to determine whether the capability exists or not.
In Experience Builder
Is the image below what you are trying to achieve.
Not quite. Maybe this illustration will help:
You could use the "Unique (predefined)" option under "Select source type" (in your screenshot). This would entail adding all the abbreviations one-by-one (as codes) along with their full names (display values). There is no way to designate a field simply to display but not filter on--there has to be a value connection, it can't just be a record connection.
Thanks, @NicoleJohnson . I had the same thought too but was trying to steer away from that solution since there will be more unique values added to the data as it is collected. I would then have to update the predefined list frequently. My hope was something more fluid. I guess it's not possible, at least not at this point.
@AndrewBowne, if you own the layers and are working in ArcGIS Online, I'd consider making a joined hosted feature layer view, which would allow you to bring the state attributes over to the smaller geographies based on their shared abbreviation field. This does have some drawbacks though, mainly that if you want to change either of the parent layer schemas after you've made the view, you have to either a) delete the view and re-source the apps that are consuming the view, or b) temporarily break then put back together the view's service definition. I haven't seen tutorials for either of these online; the former is pretty straightforward with ArcGIS Assistant, and the latter quite a bit less so but means not having to re-source anything.