# New Lookup Concept 🔍
**URL:** https://community.glideapps.com/t/new-lookup-concept/20060
**Category:** Feature Requests
**Created:** [December 18, 2020, 11:54pm UTC](https://community.glideapps.com/t/new-lookup-concept/20060 "2020-12-18T23:54:02Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)
#### Post date: [December 18, 2020, 11:54pm UTC](https://community.glideapps.com/t/new-lookup-concept/20060/1 "2020-12-18T23:54:02Z")
@david @mark @Jason
What about **Lookup** columns look like this:
I see everytime we gotta create a single/multiple relation to it. Thinking about easier ways to use the platform and how many people is not familiar with Lookups or Relations… How about we join the two?
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [December 19, 2020, 12:18am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/2 "2020-12-19T00:18:20Z")
+1. This is the actual way people are used to in the Sheets with Vlookup.
---
### Author:  [@kyleheney](https://community.glideapps.com/u/kyleheney)
#### Post date: [December 19, 2020, 12:21am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/3 "2020-12-19T00:21:00Z")
I like it! Curious though… is the thought that this would act as a relation in the sheet too, or would a separate relation column still need to be added to perform other relation-type stuff (like for inline lists, etc)?
---
### Author:  [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)
#### Post date: [December 19, 2020, 1:31am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/4 "2020-12-19T01:31:24Z")
No @kyleheney. We would still have the Relation column, but to use Lookup columns today we **must** have any type of Relation, and that’s what exactly confuses people who are starting on the platform.
So, the thought would be when we’d create a lookup column, we chose the “relation” inside of Lookup configurations (second screenshot of the topic), just telling glide **where** we’re going to bring the value from.
Today we do it, but separately.
---
### Author:  [@david](https://community.glideapps.com/u/david)
#### Post date: [December 19, 2020, 2:01am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/5 "2020-12-19T02:01:17Z")
I see—choose an existing relation, or make one in the lookup column? Interesting.
---
### Author:  [@david](https://community.glideapps.com/u/david)
#### Post date: [December 19, 2020, 2:02am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/6 "2020-12-19T02:02:19Z")
We actually want to get rid of the Lookup column entirely, and create something we call “Inline Lookups,” which would let you choose any property of a any relation when picking a value, anywhere. These would also be writeable.
---
### Author:  [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)
#### Post date: [December 19, 2020, 2:03am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/7 "2020-12-19T02:03:42Z")
Even if it’s single or multiple?
---
### Author:  [@Pablo\_books](https://community.glideapps.com/u/Pablo_books)
#### Post date: [December 19, 2020, 2:24am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/8 "2020-12-19T02:24:12Z")
Ah, just like webflow does it. I think that’s a good idea.
---
### Author:  [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)
#### Post date: [December 19, 2020, 2:24am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/9 "2020-12-19T02:24:53Z")
Would this be similar to my feature request of inline templates/tags too? For instance, in a custom text field, be able to say something like Hello, {name} where {name} is the value in the name column or from a lookup?
---
### Author:  [@Pablo\_books](https://community.glideapps.com/u/Pablo_books)
#### Post date: [December 19, 2020, 2:29am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/10 "2020-12-19T02:29:49Z")
In your feature request, would that be a replacement or alternative to a template column?
---
### Author:  [@Drearystate](https://community.glideapps.com/u/Drearystate)
#### Post date: [December 19, 2020, 2:50am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/11 "2020-12-19T02:50:43Z")
Sounds way better, so lets get that rolling and ready for XMAS day:)
---
### Author:  [@Amal](https://community.glideapps.com/u/Amal)
#### Post date: [December 20, 2020, 9:14am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/12 "2020-12-20T09:14:42Z")
Awesome! cant wait for this!
---
### Author:  [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [December 20, 2020, 9:33am UTC](https://community.glideapps.com/t/new-lookup-concept/20060/13 "2020-12-20T09:33:41Z")
> [@david](#):
>
> We actually want to get rid of the Lookup column entirely, and create something we call “Inline Lookups,” which would let you choose any property of a any relation when picking a value, anywhere. These would also be writeable.
@david this is an exciting development. Do you mind if I ask if this is very far away? (weeks? months?)
I’ve started working on a translations template concept that’s going to rely _heavily_ on lookups, and now I’m wondering if I should icebox the idea for a little while…
---
### Author:  [@david](https://community.glideapps.com/u/david)
#### Post date: [December 20, 2020, 2:01pm UTC](https://community.glideapps.com/t/new-lookup-concept/20060/14 "2020-12-20T14:01:00Z")
Sorry, we will never get rid of the Lookup column. I meant to say, we want to make a better alternative.
---
### Author:  [@Lucas\_Pires](https://community.glideapps.com/u/Lucas_Pires)
#### Post date: [December 20, 2020, 8:48pm UTC](https://community.glideapps.com/t/new-lookup-concept/20060/15 "2020-12-20T20:48:07Z")
I agree