How do I adjust the height of a table so that it requires pagination? No matter what I do, the table scrolls in one view to the bottom of the table. If it’s a long table, that’s a long scroll. I don’t want that - I want the user to be able to tab the “right arrow” button to paginate.
Hi @kenclem,
Select the list → Left pane → Advanced Options → turn on Manual Pagination and select page size.
This works for custom lists, see the video in “Pagination” section here: Lists | Adalo Resources.
Best,
Victor.
@kenclem as I can guess you are using an external collection as a table source (as the name is Gas Price API).
For External collections unfortunately you can’t do pagination with Adalo’s built-in features. E.g. in a table with Adalo collection you will see something like this:
For the External collections you may try implement pagination manually if API supports it. But you will have to keep track of the offset by yourself and left/right buttons(icons).
Best,
Victor.
P.S. My original answer referred to the lists (not table lists), I wonder if the question text was modified after I answered.
Since there are so many more features available when an internal collection is used, is there a way to sync an internal collection with an external database (which would eliminate the need for API calls to an external database)?
P.S. No need to wonder. It was not.
I do always pagination but i was wondering if there is an option to fix the amount of items and let the list load when users scroll without, in example, make the rectangle in the back height changes.
Width is possible to fix but no height(?)
@kenclem well, you will have to use Collections API (which requires higher plan) and you will have to create a sync function(s).
Technically this is possible and I’ve implemented this several times. IMO this approach is ok when you don’t have a lot of incoming changes, don’t need realtime and don’t have to sync back; otherwise the whole flow becomes complicated.
I’d say that if API supports pagination, it might be worthwhile exploring this path rather than syncing. There were some threads in the forum about Airtable pagination, they can give the idea on how to implement it.
Then probably I need to stop answering multiple messages at the same time not to confuse topics 
Best,
Victor.
Thanks Victor!
I got what you say and I will keep with pagination in order to avoid such a changes in components dimensions.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.