# Array Column as options in a choice component?
**URL:** https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108
**Category:** Feature Requests
**Created:** [June 19, 2020, 1:13am UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108 "2020-06-19T01:13:04Z")
**Posts on this page:** 8
**Page:** 2
### Author:  [@Rasha](https://community.glideapps.com/u/Rasha)
#### Post date: [July 17, 2020, 11:48pm UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108/21 "2020-07-17T23:48:38Z")
you voted for this, no?
---
### Author:  [@Rasha](https://community.glideapps.com/u/Rasha)
#### Post date: [August 2, 2020, 4:06am UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108/22 "2020-08-02T04:06:21Z")
Hey @Mark - I put together an app to illustrate the challenges, redundancies, and extra processing that can be eliminated by having an array column for the choice component.
The app is a simple list of products in 3 different sizes: [https://arraycolumn.glideapp.io/](https://arraycolumn.glideapp.io/)
Two scenarios. The first speaks to the current state of affairs. The second borrows from a [workaround](https://community.glideapps.com/t/solved-dynamic-product-variants-in-choice-component/12344) introduced by @Jeff_Hager and @ThinhDinh. It may be suitable for a vendor with a limited product catalog but doesn’t scale.
Time/effort spent working around this simple limitation is rather high and it has cascading effects. If there’s a way to achieve that workaround within the data editor, I’d like to know. Otherwise, can you suggest something more efficient if an array column for choice is not a feature Glide would consider valuable?
---
### Author:  [@gvalero](https://community.glideapps.com/u/gvalero)
#### Post date: [August 2, 2020, 4:23am UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108/23 "2020-08-02T04:23:24Z")
Hi @Rasha
I think this new tool could help to this case (Join Texts):
> [@Write an array column (via Lookup) to Google sheet](https://community.glideapps.com/t/write-an-array-column-via-lookup-to-google-sheet/13062/32):
>
> but the solution is close @Mark!! (well, depending on of effort to make changes in Glide code). Here my 2 cents: To allow a Template column to work with Lookup (single or multiple relations). I know the blank spaces inside array can generate a headache (e.g: Red, , Green, , , Blue , , ) to understand/handle the result but if those spaces can be eliminated we could have a clean list ready to work in anywhere (Red,Green, Blue) As I wrote days ago, an array column with multiple valu…
Now I can understand the problem of using an array column in a choice component (the blank spaces/fields) but with the **Join Text** tool, it could be the solution using the newline as the separator list inside array.
Mark here has the last word!
Saludos
---
### Author:  [@Mark](https://community.glideapps.com/u/Mark)
#### Post date: [August 2, 2020, 2:25pm UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108/24 "2020-08-02T14:25:39Z")
I see the point.
---
### Author:  [@Rasha](https://community.glideapps.com/u/Rasha)
#### Post date: [August 2, 2020, 6:47pm UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108/25 "2020-08-02T18:47:51Z")
I checked it out in staging. **Join Text** allows me to combine all size/price options for a product (e.g., **Small ($5.00/pc), Medium ($10.00/pc), Large ($20.00/lb**) in the data editor instead of the sheet. But, I still need to write them to the ProductTwo sheet and re-split for the ARRAY computation which relies on a second sheet. The trouble with choice is not blank spaces or fields.
---
### Author:  [@gvalero](https://community.glideapps.com/u/gvalero)
#### Post date: [August 2, 2020, 7:23pm UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108/26 "2020-08-02T19:23:12Z")
I know your point of view but now try to see the case from 200 mt tall.
Maybe you don’t have problem with a choice and array because you build it manually (Price1, Price2, Price3 —\> Price) and surely you won’t have blank spaces or fields in that list.
But what if, the array is dynamic based on a multiple relation?
You won’t have to create new columns, the items list (or size types list) is created automatically with every selection or operation and the choice component will use this list w/o problems.
I have also your same problem with Pizza dishes (large, medium or small size) and I’m try to kill 2 birds with one shot! 😇
Feliz día Rasha
---
### Author:  [@Rasha](https://community.glideapps.com/u/Rasha)
#### Post date: [August 2, 2020, 8:02pm UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108/27 "2020-08-02T20:02:35Z")
I understand your perspective but we’re not standing atop the same mountain. I do very much have a problem with choice: not being able to use array columns. I understand the “blank space” conundrum but that’s not the bottleneck. We’re missing each somewhere here 🙂
I’m not entering Sizes or Prices manually. Those are entered by the “distributors” using the app along with several other Product criteria.
> [@gvalero](#):
>
> But what if, the array is dynamic based on a multiple relation?
Can you elaborate on that? How are those multiple relations set up? No matter how you look at it, it’s additional work/workarounds.
No killing birds 🙂 We can both advocate for fixes/improvements. Cheers.
---
### Author:  [@AjBruce](https://community.glideapps.com/u/AjBruce)
#### Post date: [March 30, 2021, 1:43am UTC](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108/28 "2021-03-30T01:43:31Z")
This would be great!
[Previous page](https://community.glideapps.com/t/array-column-as-options-in-a-choice-component/11108.md?page=1)