Finding my app is outgrowing a few things, help with glide tables and pagination

Ask for Help
1

Hello Gliders!

Can you help me for a minute, I don’t have glide big tables setup as I like the instant interface with glide tables etc… now with that out of the way can you help me with this question:

Can you use pagination in an http request for Glide Tables? It appears that when i request get rows in make.com it spits out ALL the columns, and ALL the rows. The dataset is too large to work with, over 12MB, and nearing 8000 rows, problem is the data is truncated and I can’t work with it, all it says is Data is too large.

What i’ve done to speed things up and not consume massive data useage in make.com, is I use the datastore to store all the rowID’s of the table I want to use, its way faster in make.com to do this internally, but what I am trying to accomplish is a routine run scenario that creates a true up of this data base to the glide database. Users cannot add rows to my app, it happens all through an API

2

No. Well, yes and no. Get Rows does support NEXT/CONTINUATION, but you cannot control how many rows are returned with each call. It will always return all rows, up to the maximum of 10,000.

LIMIT is supported with queryTables, but that only works with Big Tables.

If I was you, I would consider moving to Big Tables. My general rule of thumb is that I’ll use Big Tables for anything I expect to grow larger than 10k rows.

1 Like