Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Sorry for two comments. I forgot to add. The workaround was to use the Web Site "data" so that /data/collections is used. It's not well documented but you can search the data, and the response is always JSON. This "data" option has been so successful for us, we stalled our XPages recode, and switched to this HTTPRequest/AJAX technique instead - cheaper than recoding.
We hit this same wall. That said, we do this in class Domino HTTP (w/o XPages) already via HTTPRequest (AJAX) calls. See http://liftandshift.org/LiftShift/LiftandShift.nsf/webPgT!OpenView&pc=Cloud. Turn on Inspect /Developer Tools in Firefox/Chrome/Safari and then do a request. You'll see a request like: http://liftandshift.org/LiftShift/LiftandShift.nsf/api/data/collections/name/webPgT?search=FIELD+WP_CategoryPage+CONTAINS+Cloud&page=0&ps=10. This returning results in JSON format, which we then parse with a local JS library to update the page w/o a full service call. We use this technique for filtering (e.g. click Webinar on that page), and to do scrolling pages page one for additional content/pages to load.