Glide Get Row API not returning app basic columns

Hi guys,

I am using Make.com to run a scheduled automation and I ran into an issue.

Looking at Glide API, I should be getting all basic columns into Make. While I am getting just a portion of them. Any ideas why?

Glide API

Make “Get Row” module
Screenshot 2024-08-03 at 17.13.17

I am missing quite a few core ones, and I have managed to retrieve the field types before on other tables (boolean, date-time, number, etc.)

Is this a known bug?

Any columns that are empty won’t show up. If that’s the case, you can temporarily add some dummy values into those columns and then they should show up.

1 Like

Thanks Darren, once again :slight_smile: You’ve been of great help on the last few posts I had.

Is this by design? Are there any updates coming to this? If no, where can I submit a feature request?

Is there a reason you need to retrieve columns where there’s not a value?

There are a couple of undocumented endpoints that you can use to query table meta data. See below:

2 Likes

Yeah in fact there is. So basically I am working with a client that wants to automatically assign yearly leave. And for one of the types the condition varies depending on whether they have children or not. So true/false here is important because they take different routes. If I can’t retrieve the field, I can’t configure routes. I updated it into a text field, but boolean fields are a lot less dynamic and would work better.

Thanks Darren!

I believe you can have conditions for it whether it exist or not in the payload.

If fieldName is true then go this route, if fieldName is not true or fieldName does not exist then go this route.

True although then I need to get those fields in first. If boolean is false for all records right now I have to create dummy data to design the flow and with multiple boolean fields in multiple tables that feels unnecessary inefficient.

Glad there’s a workaround though I would prefer to not have to have a workaround if you know what I mean.

You can copy an existing field name, paste that somewhere, and then edit to the field name you want to refer to.

1 Like

Yeah I think’s fine. I am more saying my point is if the API call would by default return everything, workarounds wouldn’t be needed.

Happy you guys helped me find a way, just wish there was a way without the workaround, is all.

1 Like

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