Sort columns - GlideTable

Hi there.
Is there a way to sort a column on GlideTable?
I have several rows unsorted, and i need to sort them on GlideTable not in the app.

Do you actually need them sorted in the table, or just in the app UI?

duh, ignore that. I can’t read :crazy_face:

1 Like

There’s no way to sort a Glide Table yet.

1 Like

wish I knew this before I started without a google sheet :frowning:

Just out of curiosity, why do you need your rows sorted in the Glide Table?

I’ll share a case I’ve ran into. My particular issue was fixed, so it’s not really an issue for me at the moment, but if you’re building dynamic html tables or quickchart urls, then it is nice to be able to sort since that is logic that is handled in the data, rather than the interface.

I explain an old bug that I found a while back and was fixed, but does present a case for sorting of some sort within the table, or at least through relations.

2 Likes

Actually yeah - very good point. And this is something that’s also occurred to me recently. I do a lot of that as well (building dynamic tables using joined lists), and just a day or two ago I was wondering what I would do when I hit a case where I need to order the data in the table (I haven’t yet).

I haven’t put much thought into it, but I’m not sure there would be a solution for that? I guess if the Glide Table is linked to a GSheet you could sort the GSheet and then sync it, but that wouldn’t help if you need dynamic sorting.

Sorting through relations would be ideal - perhaps a candidate for this weeks live coding session? :wink:

1 Like

When entering a lot of data directly into the table I easily forget if I have already entered something. I have been entering duplicate data. Sorting would help me easily view this without individual searches.

Okay, here is a little trick you can use to help avoid that:

  • Let’s say you have a column called “Name”, and you want to avoid duplicates in that column
  • Create a multi-relation column that links the Name column to itself (rel-name)
  • Create a rollup column that does a count via that multi-relation (count-name)

Those two by themselves are enough to identify duplicates (count-name will be greater than 1), but to make it a bit easier to visually spot duplicates, create a 3rd if-then-else column:

  • If count-name is greater than 1, then true
  • Else blank

So as soon as you enter a duplicate name, that column will immediately be true for that row

1 Like