For information, the data is already sent with a pagination from Baserow (100 items by endpoint) and when we want to make a pagination with Weweb, it doesn’t work (I tried to set 25 items in the “Sort, Filter and Pagination” configuration panel).
On Baserow documentation API, it is written :
“In order to list the rows in the table, a GET request must be sent to the access point of the table. The response is paginated and by default the first page is returned. The desired page can be retrieved by defining the page and size request parameters.”
you would like to be able to fetch the other 80 items
Is that correct?
If that’s the case, I would recommend you start by trying to make the API call to baserow that will return all 180 items or the 80 items on the second “page” in Baserow.
You could use a free tool like Postman to test your API calls. It might be slightly easier than doing it in WeWeb and at least, you’ll know for sure if the issue is coming from Baserow.
Looking at this thread in the Baserow forum, you might need a special plan to get access to more than the first 100 items via API.
Because we’re experiencing the same, here.
We resolved to selfhost Baserow to go beyond that limit (of 200 actually), but the issue remains, and we don’t really know where to change the settings to allow more than this small number.
@Joyce for static collection pages, is there a way to apply a GET request only when the page is loaded?
This to only fetch the records needed on the loading page, instead of all the records of the table.
