Query Widget: More Features Displayed in Results?

[AdamRepsher_BentEar]

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

[TianWen]

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.

[AdamRepsher_BentEar]

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

[AdamRepsher_BentEar]

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

[JonathanPollack]

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

[AWipf]

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!

[Kklitt]

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!

[TianWen]

@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!

[CaseyCook3]

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