We have a Constellation application where a List View needs to display transaction data from an external REST API. The API returns a maximum of 20 records per request and requires a pageNumber to retrieve subsequent records.
For example:
pageNumber=1 → records 1–20
pageNumber=2 → records 21–40
What is the recommended/supported approach to handle this pagination in Constellation?
Can we either:
Implement server-side pagination, where the next page number is passed to the Data Page/API as the user loads more records, or
Implement client-side pagination, where subsequent API results are retrieved and appended to the existing List View as the user selects “Load More” / scrolls?
We would prefer to use standard Constellation capabilities without custom JavaScript, if possible.
Are there any supported configurations, extension points, or reference implementations for this scenario?
To clarify, the approach described in the article is the supported Constellation approach for handling paginated REST APIs.
Constellation tables do not provide traditional pagination controls (for example, page 1, 2, 3, Next, Previous). Instead, they use infinite scrolling, where additional data is requested automatically as the user scrolls through the list.
For an external REST API requiring pagination, the supported pattern is to enable Advanced Query options on the REST connector and map the pagination parameters expected by the API.
In your case, this should be relatively straightforward since the API only requires a pageNumber parameter. You can pass the value from QueryPage.paging.pageNumber to the REST endpoint, allowing Constellation to request the next page of results automatically as the user scrolls.
If by “another approach” you mean implementing traditional page navigation controls with users explicitly selecting page 1, 2, 3, etc., that is not a standard capability of Constellation tables. The recommended approach is to integrate the API with Constellation’s infinite scrolling model.