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.
Dear user,
We appreciate your valuable feedback and the ideas you’ve shared with us. As part of our ongoing efforts to improve our products and services, we are streamlining our idea management process.
To ensure we focus on the most relevant and impactful suggestions, we will be closing all ideas raised before 1st January 2024. However, we encourage you to submit any new or existing ideas that are still important to you through the ideas portal as before.
We have implemented new processes that will ensure newly raised ideas are dealt with efficiently and effectively.
Thank you for your continued support and input—we truly value your contributions.
Best regards,
Andy
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