Too many Values?

Question

I've been tasked with developing a proof of concept, duplicating a desktop-based "property browser" which was delivered by a contractor some years ago.  With my other work being based in AGOL, initially I considered Web AppBuilder , Dashboards, and Instant Apps as the most direct development options.  However, ArcGIS Web AppBuilder will retire in the fourth quarter of 2025 and Experience Builder appears to be the replacement.

The central function of our "property browser", must be a "pick list" or category selector which drives the filtering of ~354,000 parcels in a polygon feature set.  This "pick list" or category selector must accommodate ~1,500 appraisal areas which are assigned to each parcel record.  Our "property browser" must allow the user to select which parcels are displayed, grouped by a single appraisal area, or by multiple appraisal areas.

I got this set up quickly in AGOL Dashboards, but I can’t do it fully in Experience Builder. This limit within Experience builder can be seen in the attached image.

So what is the magic cut-off number?

I could use some help in navigating ESRI’s tech support world in order to determine:
1. Is the limitation with group filters in Experience Builder, as described above and unchangeable?
2. What are our other options, within ESRI, to have the functionality that we need in an application develop environment?

JPrescott · Answer

Hi @Ke_Xu,

We have been experiencing the same warning about "too many values" when trying to use the pill selector in filter widget in experience builder (Enterprise 11.3).  Thank you for confirming that this is due to a built-in limitation.  What is the specific cutoff number for unique values that would enable use of the pill selector?  We have 30 unique values and would like to know if we are close to the cutoff, since we may be able to massage our data to fit this limit.

kxu · Answer

Hi @TimothyHoeflich,

When Pill selector style is used, it has some limitation to the number. It is by design.

This style only applies to a small number of unique values, making it easy for the user to select values directly.

Thanks,

Ke

Jeff.Thompson@arlingtontx.gov_arlingtontx · Answer

The Filter Widget has some limitation to the number of buttons it will create. I don't know the exact number, but your design would create way too many. The buttons would fill the entire screen and then some. I don't think the dropdown style has any such limitations, but for the sake of your users, use the User Input and Ask For Values Options. This will give them a text input which will be much easier to use than hunting through thousands of items in a dropdown.