wow, you have sheets/tables with 100+ basic (non-computed) columns?
That’s pretty jaw-dropping, I can’t imagine how difficult that must be to manage.
I have tables that have several hundred computed columns, but never that many basic columns. The most I would ever have is around 20-30. Once I get to that number, I start looking for ways to normalise and break it into multiple sheets/tables.
1 Like
well, just checked and one table ends on BY(77 rows). Managing Add Row and Set columns values are difficult here 
But even with 20-30, it’s not friendly for us.
Oh, and I wish that Glide team can add the switch “Show Filled Only” or “Show Filled at first” for these actions. In this way, it would be easier to analyze and debug logic.
Why normalise is not an option for Glide?
I believe that it’s because you have to create a Lookup for each column from normalised tables to refer to that value.
Glide definitely should allow setting component properties with columns from related rows.
Or at least do as Airtable: When you add Relation column - Airtable shows popup with checklist of column names from that table and you can instantly setup Relation and columns you need for Lookup(10-20 or none)
Absolutely agreed. These are features that many of us have been requesting for quite some time.
I think that “inline lookups” may be coming at some point, which will definitely save on lookup columns (and possibly make them redundant).
Setting column values through multi-relations has also been requested, but I don’t know if that’s on the radar or not.
3 Likes
Yay! Is it just me or is the GDE back “on form”! I need to hug somebody! Maybe even @david …
2 Likes
I wasn’t game to say anything… but, yes…
Great
Ok. I will reserve the “David Hug” for another time! 
This topic was automatically closed after 4 days. New replies are no longer allowed.