API get rows not parsed anymore?

General
1

Hello everyone,

Has something changed with the get rows API request? Since this morning, the rows are not parsed in Make whereas it has always been the case, resulting in errors in the next steps.

Before changing our scenarios by adding a parse element, I want to make sure that it’s permanent?

Kind regards

Lucas

2

Something I did not see :

logstatus - Data too long. The log content was cut. The size of the original buffer was: 4835534

I assume our table got to big for a simple get rows?…

3

Yeah, seems to be the case. There’s a limit for the buffer to be sent out.

1 Like
4

Thanks for the confirmation Thinh.

I guess that there is no other native solution in Glide rather than upgrading to the business plan in order to have access to the API and querying?

5

If you want query through the API, it would only work with Big Tables. So you must have access to a plan which has access to both Big Tables and API.

1 Like
6

You’re right, thanks Thinh.

I share what I did in the meantime, in case someone needs it : I created a simple helper table in google sheet (100% of our db is Glide table otherwise), where I store each item rowid, as well as other criteria, A,B,C etc (the ones I need for the query).

In our scenario, it allows us to query the Google Sheet with A, B, or C, find the corresponding row, and then use our Glide rowid to do a direct edit of the row in Glide.

Not ideal, but it’s a medium term workaround. We are kind a hesitant to migrate toward Big tables, as soon as we try, we encounter feature limitations.

1 Like
7

if your using make.com, and want to make this faster, use their internal data stores instead of google sheets, it will be near instant. Create a new datastore with the row ID that syncs your reference data when a row is created. then use make.com to do a “lookup”

2 Likes
8

How would you update this? I assume you have a flow in your app to CRUD those Sheet rows when you CRUD the Glide Tables rows?

9

Thanks fo the tips, I’ll try to implement this!

10

Items in this Glide table are only added via Make. So we indeed have a scenario that creates everything we need related to our business (glide sub element, make API request to external services) and then we store all the IDs (from external services) linked to our Glide item in the corresponding Glide row, but now also in the google sheet that we use as this helper table.

1 Like
11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.