# Glide / Make.com : How to see column names?

**URL:** <https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516>\
**Category:** Ask for Help\
**Created:** [April 12, 2024, 11:37am UTC](https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516 "2024-04-12T11:37:53Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sumgii](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@sumgii](https://community.glideapps.com/u/sumgii)\
**Post date:** [April 12, 2024, 11:37am UTC](https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516/1 "2024-04-12T11:37:53Z")

</div>

I’m using the new integration with Make to get rows from my glide user table. When I do this I see the following:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/a/1/a19dcd6a486d946f8942f8f7a079e331fb5bb7e1.jpeg)

It’s odd that some of the columns are shown as name (name/email) and others by an id (JfvSi etc). Is there a way to force the names to show? The order doesn’t match dataview either so I am resorting to guessing - not easy with things like date columns.

Also, If I wanted to pull a subset of rows (example where user\_status = activated) I can’t see a way to select just those. I am currently getting all rows then using FlowControl to decide which to act on. Doesn’t seem too efficient. Is anyone doing this in a smarter way?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [April 12, 2024, 2:35pm UTC](https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516/2 "2024-04-12T14:35:49Z")

</div>

> [@sumgii](#):
>
> It’s odd that some of the columns are shown as name (name/email) and others by an id (JfvSi etc). Is there a way to force the names to show? The order doesn’t match dataview either so I am resorting to guessing - not easy with things like date columns.

You can check those IDs in your data view. Right click on the table \> Show API \> Add rows/Edit rows.

> [@sumgii](#):
>
> Also, If I wanted to pull a subset of rows (example where user\_status = activated) I can’t see a way to select just those.

The API does allow you to do that with Big Tables using queries, the module doesn’t seem to allow you to do that as of now, and I don’t know if it’s feasible for normal Glide Tables.

---

<div class="post-metadata">

**Author:** ![sumgii](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@sumgii](https://community.glideapps.com/u/sumgii)\
**Post date:** [April 12, 2024, 5:28pm UTC](https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516/3 "2024-04-12T17:28:29Z")

</div>

That showAPI is really handy, thanks! Unfortunately it highlights that the issue I really have is that I can’t use the computed fields (as you mentioned in the other thread). That is very annoying.

I really don’t want to repeat the logic in Make as I can see those getting out of sync.

I was trying to use the computed columns to filter out the rows I don’t need. Maybe I am going about it backwards.Am I missing a way to add a “where” to the get Rows?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [April 12, 2024, 5:36pm UTC](https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516/4 "2024-04-12T17:36:45Z")

</div>

> [@sumgii](#):
>
> Am I missing a way to add a “where” to the get Rows?

That’s only possible with Big Tables.

---

<div class="post-metadata">

**Author:** ![sumgii](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@sumgii](https://community.glideapps.com/u/sumgii)\
**Post date:** [April 12, 2024, 5:42pm UTC](https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516/5 "2024-04-12T17:42:47Z")

</div>

ah, that’s the answer I didn’t want. Unfortunately that needs Business package, which is currently out of reach for this project.

I’m currently reading up on helper tables to see if they are an option.

All I want to do is to to the equivalent of

select \* from users where account\_status = live and due\_date \> now and last\_email\_date \< due\_date

so that I can email or slack those users with a “your thing is due” message.

Any other approaches worth me taking a look at?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [April 12, 2024, 11:55pm UTC](https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516/6 "2024-04-12T23:55:25Z")

</div>

> [@sumgii](#):
>
> select \* from users where account\_status = live and due\_date \> now and last\_email\_date \< due\_date
> 
> so that I can email or slack those users with a “your thing is due” message.
> 
> Any other approaches worth me taking a look at?

Are any of those columns computed? If they are basic, you can use a filter in Make.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [April 13, 2024, 10:16am UTC](https://community.glideapps.com/t/glide-make-com-how-to-see-column-names/72516/7 "2024-04-13T10:16:22Z")

</div>

> [@sumgii](#):
>
> so that I can email or slack those users with a “your thing is due” message.
> 
> Any other approaches worth me taking a look at?

The following is the approach that I have taken, which works for me:

- My App is 100% Glide Native tables
- I created a Google Sheet that is not directly connected to the App.
- The sole purpose of the Google Sheet is for managing email reminders
- The way it works is:  
– On a daily basis, I fetch the table data that I need via the API using Apps Script  
– I then process the data, figure out which users need reminders, and trigger a notification email via a webhook to Make

It’s a little convoluted, but it gets the job done.
