Make ADF pagination functionality more robust to handle more robust pagination rules using variables and comparison operators
Pagination in ADF V2 REST API doesn't work for many SaaS applications for e.g. when the response contains the current page number and total page count values. Currently we are using complex Until loop with two variables to overcome pagination limitations and not able to use delivered pagination rules at all. It would be great if in the pagination rule itself we can compare the current page number with total page count to paginate rather than using so many variables and until loop.
Is there any plan to make pagination functionality more robust to handle allow more robust pagination rules using variables and comparison operators?
Carsten Bredsdorff commented
Additionally, many APIs (Zendesk, for example) just return the current page for the $.next_page json element when it reaches the last page. There is an additional element called $.end_of_stream which is a true/false field. If this is true, the end of the pagination has been reached; however, this can't be evaluated via the current ADF Pagination rules functionality. To me, more robust means the ability to evaluate multiple json elements for end of pagination.