# How many is too many columns?

**URL:** https://community.glideapps.com/t/how-many-is-too-many-columns/65624
**Category:** Ask for Help
**Created:** [August 31, 2023, 1:36am UTC](https://community.glideapps.com/t/how-many-is-too-many-columns/65624 "2023-08-31T01:36:54Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [August 31, 2023, 1:58am UTC](https://community.glideapps.com/t/how-many-is-too-many-columns/65624/3 "2023-08-31T01:58:28Z")

</div>

> [@Chassy](#):
>
> This seems inefficient as far as process goes, and I feel like there should be a more direct way to access this info than to add a lot of lookup columns.

Please add your vote below:

> [@Select values from relations just like "User \>" (Inline Lookups)](https://community.glideapps.com/t/select-values-from-relations-just-like-user-inline-lookups/26092):
>
> Just like we can choose a value from a user profile sheet during if/then/else columns, template columns, filtering/visibility conditions, etc, would love to be able to do the same via relations. It would cut down on SO MUCH app bloat. @david @mark @tristan Here’s a mockup:

As @ThinhDinh mentioned, 50 computed columns is generally nothing to worry about. It just depends on what they are doing and how many rows they are operating on. But things like relations/lookups/templates should be no problem at all.

---

_[View the full topic](https://community.glideapps.com/t/how-many-is-too-many-columns/65624)._