topic Re: Query Widget: More Features Displayed in Results? in ArcGIS Experience Builder Questions

Query Widget: More Features Displayed in Results?

AdamRepsher_BentEar — Thu, 28 Jul 2022 14:51:23 GMT

Hi all,

In ArcGIS Online, I am attempting to display more than 100 features from an Experience Builder Query widget in its Results section:

I need all results to show up here (as well as on the map). I can use the scroll bar on the side, and repeatedly scroll it down to the bottom and eventually, I have all records, but this is not acceptable for the end users:

I have tried to change the Page Size within the Data-Feature Layer Settings - Records tab - Page Size.

Is there a way to show more than 100 records in the query result?

Thank you,

--Adam

Re: Query Widget: More Features Displayed in Results?

Kklitt — Fri, 07 Oct 2022 18:03:18 GMT

Hi Adam, did you find a solution to this? I'm dealing with the same issue.

Re: Query Widget: More Features Displayed in Results?

AdamRepsher_BentEar — Fri, 07 Oct 2022 19:34:18 GMT

Hi @Kklitt ,

Sadly, I did not. In fact, I had so many needs not met with Experience Builder - I took the project to Dashboards. I am really trying to embrace EB, but it keeps letting me down.

Re: Query Widget: More Features Displayed in Results?

sumit9135 — Tue, 08 Nov 2022 11:19:26 GMT

In ArcGIS server manager, increase Maximum Number of Records Returned by Server of the service.

Re: Query Widget: More Features Displayed in Results?

AdamRepsher_BentEar — Tue, 08 Nov 2022 12:53:53 GMT

Yea - I wish it were that easy, but it isn’t. The default there is a lot higher than 100. The problem is within the EB widget.

Re: Query Widget: More Features Displayed in Results?

TianWen — Mon, 12 Dec 2022 02:10:06 GMT

The feature has been implemented for the 10.3 release. Thank you!

Re: Query Widget: More Features Displayed in Results?

AWipf — Thu, 05 Jan 2023 22:49:26 GMT

Is this feature being added to the next version of Developer Edition as well, and when might that be released if so? I'm having a similar issue in Experience Builder Developer Edition 1.10. Thanks!

EDIT: It looks like the November 2022 / 10.3 AGOL release should be equivalent to Dev Edition 1.10. In the "What's new" post for Experience Builder for November 2022 I see the following:

Query widget—You can now make all results expand by default. At runtime, users can now choose how many results to display per page using a drop-down menu or by entering a number.

In my Dev Edition app, I can indeed force more than the default 100 records from my query results to display, but seems like it has to be done by the end user, and is not very intuitive:

My first inclination as a user is to use the dropdown for the results per page, which caps out at 100. At this point I'd think I'm still stuck with 100 records max:

But you can actually click on the number and increase this above 100; here I've set it to 2000 to mimic behavior that lots of users are used to (default 2000 max records returned by the server on many services) but any number larger than 3 digits gets cut off which could add more confusion. It does successfully display all 330 records from my query though:

You're also stuck with the multi-page result format to be able to increase the number of results displayed. If I change it to single-page I found that this actually still only displays one "page" worth of records (so by default, 100) even though the text indicates that all result features should be displayed:

@TianWen Is there any way to change the default number of records per page at the data source or widget level so that more results can consistently be returned by queries without any end user action? I also assumed that's what the "Page size" setting would do, but changing that appears to have no effect on this issue (note that the "Maximum" setting below apparently only applies to Scene Views):

Thanks!

Re: Query Widget: More Features Displayed in Results?

TianWen — Fri, 06 Jan 2023 07:43:58 GMT

Thanks for the feedback! When you use single-page, the widget will only show one "page" initially, but more records will be loaded if you keep scrolling down. This design is for performance purposes. Other problems/enhancements you mentioned above will be included in the upcoming release which is around the end of February. Will keep you updated. Thank you!

Re: Query Widget: More Features Displayed in Results?

AdamRepsher_BentEar — Fri, 06 Jan 2023 13:35:58 GMT

As stated in the original post, only loading the first 100 and having to scroll down for the rest - is not an acceptable result for my users.

Re: Query Widget: More Features Displayed in Results?

AWipf — Fri, 06 Jan 2023 16:19:54 GMT

Thanks for the update Tian, looking forward to the next release!

I understand the performance consideration for the single page results only loading one "page" of features initially, but I don't think I'm experiencing the expected behavior of all results eventually being shown if you continue to scroll. In my case it seems like a different 100 records are shown each time, rather than 100 more records being displayed so that after you scroll through enough "pages" all results are shown. Perhaps I've misconfigured my triggers/actions? I followed the Query widget documentation here, so have my trigger on the Query widget as "Records created" with my map as the target and the action being "Show on map", and am using layer-defined symbols:

However, the behavior is that separate sets of 100 records are displayed; I never see all of the records displayed even after scrolling down through all the "pages".

1st 100 records:

2nd 100 records:

3rd 100 records:

etc...

The previous 100 records are not being preserved and added to, but being replaced by the next 100 records. Is this a configuration issue on my end or perhaps a bug that could also be addressed in the next release if this topic is being dealt with?

Thanks!

Re: Query Widget: More Features Displayed in Results?

Kklitt — Fri, 06 Jan 2023 16:45:40 GMT

Hi @AWipf,

You're describing the same issue that I think we are all running into. Currently, there are really only three options for visualizing results when using the query widget with experience builder when the output has more than 100 results:

1. If using single-page output, the user has to manually input a number into the drop-down output results number. (This option is the best solution that's been provided so far but it isn't intuitive to the end user if they aren't prompted to do this).

2. If using single-page output, the user has to manually scroll through the results to view 100 outputs on the map at a time. Each time the user scrolls down, a new 100 populates on the map. This is confusing and doesn't give the user the full picture of the spread or quantity of results.

3. If using multipage output, the user has to manually click through pages of the results to view 100 outputs on the map at a time. This option operates similarly to option number 2.

I'm looking forward to this being updated so the query widget can be utilized similarly to how it performed in the web app builder. Thanks!

Re: Query Widget: More Features Displayed in Results?

TianWen — Mon, 09 Jan 2023 03:19:17 GMT

Scrolling to load is only designed for the single-page mode for performance purposes. For your situation, you can always choose the multiple page mode and set the page size.

Re: Query Widget: More Features Displayed in Results?

TianWen — Mon, 09 Jan 2023 06:48:13 GMT

@AWipf @Kklitt Thanks for the feedbacks. Above mentioned points are under consideration now. The team will work out a couple of enhancements for them. Thanks!

Re: Query Widget: More Features Displayed in Results?

AdamRepsher_BentEar — Tue, 10 Jan 2023 14:51:41 GMT

Again - the single page is what is needed, as well as the ability to load a lot more results than 100.
Thank you.

Re: Query Widget: More Features Displayed in Results?

AdamRepsher_BentEar — Tue, 10 Jan 2023 14:59:47 GMT

We are talking about a query that we can do other things with. We are not just looking at the table for results - we are trying to show users the results on a map or in concert with other widgets. Batching them out in groups of 100 or 200 isn't what we are looking for. We know the hit we take on the server side and know the adjustable server settings. What we are asking for here is the same kind of adjustment. Let us make the decision on how many we are loading - and we can see the performance hits from it and then we can decide if the hit is too much.
Our clients are asking for this. We are asking for this.

Thank you!
--Adam

Re: Query Widget: More Features Displayed in Results?

JonathanPollack — Wed, 31 May 2023 23:01:47 GMT

amazing you found that forcing a number above 100. Why doesn't EXB honor the page size setting for the feature layer. crazy

Re: Query Widget: More Features Displayed in Results?

JonathanPollack — Wed, 31 May 2023 23:06:11 GMT

it seems choosing the multipate mode with setting the page size never honors any value greater than 100 page size. is that true?

Re: Query Widget: More Features Displayed in Results?

CaseyCook3 — Fri, 19 Apr 2024 17:17:27 GMT

Ridiculous ESRI has this same problem in WAB, in EB for like 6 years now. Makes use cases for downloading data pretty useless.

Re: Query Widget: More Features Displayed in Results?

JustinH — Thu, 06 Mar 2025 20:31:11 GMT

Hi Tian -

I am wondering if there is a way to allow even more records per page. We are trying to spatially filter ~15,000 points to display within a polygon. Without a spatial filter like dashboards, I know this is the best I can do but allowing as many points to load as I want mean I can essentially filter everything in the polygons and display the statistics that I need in cards. This would be huge. TIA

Re: Query Widget: More Features Displayed in Results?

AndreaB_ — Thu, 13 Mar 2025 19:32:12 GMT

Hi @TianWen,

I am using AGOL ExB - I can't get the query widget to show any more than 10 results in the list? It says 59/59 but the scrolling stops and I only see 10 results. The points are highlighted on the map they just aren't in the list? Is there a new bug in AGOL ExB?

These are alphabetical and I only get to C - I'm looking for one that starts with M. You can see it in the map.