I have an app made in Experience Builder with some basic filters. The basic concept of how the filters in this app work is the user selects a subset of the data and the map and list of records update automatically. Since a recent update of Experience Builder some of my filters are no longer working correctly.
For example, one of the filters not working correctly is connected to a hosted feature layer view containing 2,464 records (points). The filter's settings are set to "Default". In the default settings window I have no filter set, the data is sorted ascending by the name of the facility, and the records settings have a page size set to 5,000 and a max record county of 5,000.
The SQL expression set on this filter is to display all of the unique values of a field containing the counties and tribal nations in Minnesota, and a second filter to display all of the unique values of a field containing the type of emergency facility.
The issue is that the first filter only displays the first five counties. The user is unable to select from the other 100ish counties/tribal nations in that field. All four of the unique values in the emergency facilities filter are displaying correctly.
At first I thought it may be an issue with the extent of the dropdown menu not accommodating a scrollbar, but I'm having the same issue on another dataset that is displaying about 80 of the 100ish county/tribal nations.
I've explored changing the filter settings from "Default" to "Upgraded from previous config" but to no avail. Which can someone please explain what the differences are between these two settings?
Also, all of the points in each of the datasets I'm filtering against are displaying on the map and in the list.
I appreciate any advice you can provide!
Best,
Zach
