Experience Builder Filter causing table to show no records, even when filter is disabled.

[MieszkoFydrych]

I have a tree layers containing over 100k trees for a city. In web app builder, I had a filtering widget that allowed users to query the trees based on several fields. I am migrating this app to experience builder but found that the filter widget and the filter in the table of attributes are causing an error.

Whenever I apply a filter with 2 or more queries at once on the layer, the map and table of attribute show 0 records. When I toggle the layer back off, the table and map continue to show 0 features. Applying just one query works. I have tested the query on the rest end point directly by going to ..../featureServer/0/query and I tested the filter in web map viewer. The filter has worked fine in both those places but it fails on experience builder. 

[andeb31]

I tested a custom filter on a dataset with only 150 features in ExB and it performed very poorly. It got there eventually, but only after a lot of buffering. I would guess that your large dataset could be giving the widget some issues. Do you need the filters to be custom? Or are there a handful of fields that most users will need to filter? You could try creating a few individual filters for each field as opposed to the custom option and see if that improves performance.