Welcome to the Alloy Ideas Portal đź‘‹ Here, you'll be able to browse improvement ideas raised by our community, vote on ideas you agree with or even raise your own ideas. We review all ideas raised and we endeavour to respond to all raised ideas.
Any ideas submitted will be immediately visible on the portal for others to vote on, please do not include anything in your ideas you do not wish to be shared with others.
Currently any data from a query will be erroring after page 100 as the API has a limit of 100 pages returned from the /api/aqs/query and /api/aqs/join endpoints. This is not practical for returns that run into well over 100 pages, which is normal for the data we use in relation to service rounds. I would suggest an increase in the limit to 200 in order to allow the full return of query info for considerations and actions.
Just wanted to provide an update on this idea. We are still investigating what options we have to increase the total number of rows the Data Explorer can view. I am going to add this to our backlog, any progress updates will be available from this ticket.
Thanks!
Hi,
Thanks for raising this idea. I'm trying to understand your requirement a bit more, would you be able to give a few more details what you are trying to achieve that's causing you to hit the limit?
The majority of our API end points are designed to work transactionally and focus on single or small groups of data items at a time, as opposed to streaming large datasets.
The sync endpoint is designed to stream large amounts of data and may be more suited to your requirements.
Thanks again!
Jon