topic Re: Filter widget only shows 5 options in ArcGIS Experience Builder Questions

Filter widget only shows 5 options

AFackler_NAPSG — Wed, 08 Oct 2025 00:39:18 GMT

Hello all,

I am seeing a problem with the Experience builder filter widget. I have a few hundred thousand records simply demoting the county and state in a single field, and I have a filter set up to show those records' county and state. There are a few hundred different combinations within this field. However, the filter widget only shows the first 5 options alphabetically with no settings that I could find to scroll through the potential filter options both in the SQL set up and in the widget itself.

The work around so far has been to manually type in the county you want to see data from, but even then it doesn't actually load until I hit "Search More", then it gives me the options I am looking for.

Is there any way to force the widget to search for all options right off the bat, or automatically "Search More" if the user types in a specified county? Thanks in advance!

Re: Filter widget only shows 5 options

Charles_Blanchard — Mon, 20 Oct 2025 21:11:15 GMT

Hi @AFackler_NAPSG,

The issue you are describing with search results in the Filter widget may originate from the feature service used to access the data. I would check the maxRecordCount and maxRecordCountFactor values in the REST endpoint for the feature service. If these are set too low, it could be limiting the ability of the widget to access enough records to give a proper set of search suggestions.

Here is some documentation about these parameters:

Query (Feature Service/Layer) - Return type and max record count

FAQ - What are the limits of the maxRecordCount and maxRecordCountFactor properties at REST?

I would suggest being cautious with any changes you make to these parameters however, as they can cause performance issues if set too high.

Associate GIS Analyst

Esri Canada

Re: Filter widget only shows 5 options

TonghuiMing — Thu, 30 Oct 2025 02:21:01 GMT

@AFackler_NAPSG Some possible reasons affecting the filter at runtime are:

- There might have been some filters added through other widgets, applying to the data source

- A filter has been set in the web map in MV

- The clause is configured to be affected by other clauses

In the builder, it will display all the records, which means that this field of your data only contains 5 records. Could you please provide your sample map & app so we can take a further look at it?

Re: Filter widget only shows 5 options

AFackler_NAPSG — Mon, 24 Nov 2025 16:26:11 GMT

Hi Charles, thanks for your reply, I finally have the bandwidth to come back to this issue.

Taking a look at the REST service, the maxRecordCount is set at 2000, and maxRecordCountFactor was set to 1. The layer I am setting the filter up on has only point data.

Re: Filter widget only shows 5 options

AFackler_NAPSG — Mon, 24 Nov 2025 16:28:58 GMT

Thanks for your reply! I was able to replicate the same behavior on another experience and with a fresh web map and experience with no filters applied, so I don't think there are any filter restrictions causing this.

I cannot provide a sample of the data because I don't have the permissions in my organization's enterprise environment to share things publicly.

Re: Filter widget only shows 5 options

TonghuiMing — Tue, 25 Nov 2025 02:00:07 GMT

@AFackler_NAPSG What is your portal version? If not related to the preset filters, I might have a thought about this.

Re: Filter widget only shows 5 options

Charles_Blanchard — Mon, 08 Dec 2025 22:57:31 GMT

Hi @AFackler_NAPSG,

It may be worth adjusting the maxRecordCount upwards, perhaps to 3000 or 4000 and checking to see whether the behaviour of the filter widget is improved or even fixed. If you are seeing improvement, and no meaningful performance decreases occur with the feature layer, you can try adjusting it upwards again through the REST endpoint.

If this does work to improve its behaviour, adjusting the maxRecordCountFactor upwards may also be available as an option to improve performance and avoid hitting the maximum value for maxRecordCount.

Please feel free to reach out if you have any questions!

Warmly,

Charles Blanchard

Associate GIS Analyst

Esri Canada