# Text component does not dsiplay computed column (lookup or template)

**URL:** <https://community.glideapps.com/t/text-component-does-not-dsiplay-computed-column-lookup-or-template/81445>\
**Category:** Ask for Help\
**Created:** [April 20, 2025, 12:41pm UTC](https://community.glideapps.com/t/text-component-does-not-dsiplay-computed-column-lookup-or-template/81445 "2025-04-20T12:41:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rob\_Cap](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rob_cap/32/87029_2.png) [@Rob\_Cap](https://community.glideapps.com/u/Rob_Cap)\
**Post date:** [April 20, 2025, 12:41pm UTC](https://community.glideapps.com/t/text-component-does-not-dsiplay-computed-column-lookup-or-template/81445/1 "2025-04-20T12:41:34Z")

</div>

Hello, I am going around in circles on this one. Any help is much appreciated.

I’ve built app to manage a series of music events.  
I have the following tables:

1. Users (Name, email, role [could be Band rep or event coordinator], phone, Band Name, event Name, …). This is for band reps, who will enter data for their band, and event coordinators, who will access this data.
2. Musicians (Name, instrument, requirements, Band name, event name, stage plot). This is where I store the band members for each band.
3. SetList (song title, artist, band name, event). Each band will enter their songs
4. Event List (event name + some info)

The event coordinator will have access to an event details page, where the coordinator will see a table with the bands participating to the event. The bands will be displayed in the order of play.

I created a Band\_Event data table where I save Band name, Order of Play, Event Name, plus a few computed columns: Relationship\_Band-rep, Lookup\_Band\_rep, Lookup\_Band\_rep\_phone, Lookup\_stage\_plot

I set up the Battle details page (visibility is Role = event coordinator).  
Source: Band\_Event  
Components: text: User/event name (which displays the event that the event coordinator is assigned to) - All good here.  
Collection Table: Source Band\_Event. Columns: Order of Play, Band name (filtered by event). Table sorted by Order of Play. - All good here.

Now we get to the sticky bit.  
When the coordinator taps on a table row with a band name, a band details page opens. In this page, the coordinator will see:

- The band name - OK  
\*\*\* The band rep name and a button to call them - PROBLEM I can select Lookup\_Band\_rep but it does not return anything, even if I see it correctly on the data table\*\*
- A table with the band members, their instrument and requirements (source: Musicians) - OK
- A table with the set list (source: SetList) - OK
- The stage plot (Image: Lookup\_stage\_plot) - OK.

 ![Screen Shot 2025-04-20 at 10.36.05 pm](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/2/6/26c70c42548f09021c8f4ea3bc5233b7c7ee8c3a.png)

Why can I retrieve correctly the Lookup\_stage\_plot but cannot retrieve the Lookup\_Band\_rep?

Let me know if I need to provide other details.

---

<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:** [April 20, 2025, 1:15pm UTC](https://community.glideapps.com/t/text-component-does-not-dsiplay-computed-column-lookup-or-template/81445/2 "2025-04-20T13:15:55Z")

</div>

> [@Rob\_Cap](#):
>
> Why can I retrieve correctly the Lookup\_stage\_plot but cannot retrieve the Lookup\_Band\_rep?

My guess would be because one is sourced via a single relation, and the other via a multiple relation.

Can you should how both columns look in the data editor please?

---

<div class="post-metadata">

**Author:** ![Rob\_Cap](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rob_cap/32/87029_2.png) [@Rob\_Cap](https://community.glideapps.com/u/Rob_Cap)\
**Post date:** [April 20, 2025, 1:41pm UTC](https://community.glideapps.com/t/text-component-does-not-dsiplay-computed-column-lookup-or-template/81445/3 "2025-04-20T13:41:24Z")

</div>

Is this what you are requesting?

Lookup\_StagePlot (image. This is working)

 ![Lookup stage plot](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/f/7ffba3ff67e6e83edbddaaaa3cec7416b67f7b39.png)

Lookup\_Band\_rep (not working)

 ![Lookup band rep](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/4/9/4970b1bf834331ed73f0b6cc498d44e2df5c0f4b.png)

rel\_band\_rep  
Relate to items where the value in: Band\_name  
Matches the value in: **Users** \>Band\_name [match multiple NOT ticked]

Now, I’ve been trying different things and I got something that seems to work (but I cannot figure out why, which makes me nervous).  
I created a relation column Rel\_Band\_musos  
Relate to items where the value in: Band\_name  
Matches the value in: **Musos** \>Band\_name [match multiple ticked]

Then a Lookup\_Band\_musos with relation column: Rel\_Band\_Musos \> Name  
which returns multiple names  
Then a Single value column, which takes the first value of the Lookup\_Band\_musos column

I can display this one and the values are correct.

 ![Lookup on Rel_band_musos instead of rel_band_rep](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/8/d/8d8f141086216791daed2dedc74558573eae7c05.png)

It seems that the issue is the relationship table (Rel\_band\_musos instead of rel\_band\_rep), but cannot figure out why, so I call it luck and it could be that it displays the correct values by chance.

---

<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:** [April 20, 2025, 2:23pm UTC](https://community.glideapps.com/t/text-component-does-not-dsiplay-computed-column-lookup-or-template/81445/4 "2025-04-20T14:23:02Z")

</div>

> [@Rob\_Cap](#):
>
> It seems that the issue is the relationship table (Rel\_band\_musos instead of rel\_band\_rep), but cannot figure out why, so I call it luck and it could be that it displays the correct values by chance.

Yes, it is.  
When you configure a relation with “Match multiple” selected, any subsequent lookups that target that relation will _always_ return an array (even if there is only a single match), and arrays cannot be used in any component that expects a string value - such as a text component.

Your single value approach works, because the single value column returns, well, a single value.

But the easier fix is to just use a single relation in the first place (Match multiple not checked).

---

<div class="post-metadata">

**Author:** ![Rob\_Cap](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rob_cap/32/87029_2.png) [@Rob\_Cap](https://community.glideapps.com/u/Rob_Cap)\
**Post date:** [April 21, 2025, 4:07am UTC](https://community.glideapps.com/t/text-component-does-not-dsiplay-computed-column-lookup-or-template/81445/5 "2025-04-21T04:07:51Z")

</div>

Thanks for explaining. A couple of things. Please tell me where I am wrong and thanks for your patience.

1. The relation rel\_band\_rep looks at the **Users** data table and returns a one to one relationship. Then the Lookup Lookup\_band\_rep retrieves the band rep name and returns an (of a single value). If I feed this to the text component, it does not show because it is an array. However the Template type should convert it to a string. Still it does not work.  
Also I can’t use a Single value as the rel\_band\_rep cannot be selected. I thought I could use it to convert a single value array to a text.

2. The relation rel\_band\_musos looks at the **Musicians** data table and returns an array (multiple values according to the number of musicians). Then the Lookup Lookup\_band\_musos retrieves the musicians names (multi value array). Then I use Single value (First) which takes the first value of the array and returns it as text. Which means, that it returns the band rep name only if the band rep entered his/her name first.  
So I’ve been lucky, but it is not a correct solution.

rel\_band\_rep has Match multiple NOT selected. It’s a 1-1 relationship and it points to the Users table.  
Why can’t I do a Lookup and then covert to text with Template or Single and use that?

---

<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:** [April 21, 2025, 6:13am UTC](https://community.glideapps.com/t/text-component-does-not-dsiplay-computed-column-lookup-or-template/81445/6 "2025-04-21T06:13:13Z")

</div>

Firstly, here is something to understand. Any time you see a value inside a lookup column in the data editor that appears inside a “bubble”, then it means the values in that column are an array.

> [@Rob\_Cap](#):
>
> The relation rel\_band\_rep looks at the **Users** data table and returns a one to one relationship. Then the Lookup Lookup\_band\_rep retrieves the band rep name and returns an (of a single value). If I feed this to the text component, it does not show because it is an array.

That doesn’t make sense. A lookup through a single relation won’t return an array, unless the target column is already an array. Question: When you look at the values for “band rep name” in your Users table, do they appear to be inside a “bubble”?

> [@Rob\_Cap](#):
>
> The relation rel\_band\_musos looks at the **Musicians** data table and returns an array (multiple values according to the number of musicians). Then the Lookup Lookup\_band\_musos retrieves the musicians names (multi value array). Then I use Single value (First) which takes the first value of the array and returns it as text. Which means, that it returns the band rep name only if the band rep entered his/her name first.

Why is that a multiple relation if you only want one value?  
By the way, in terms of what you have now, you could skip the lookup column and just target the single value column directly at the relation. But again, why not a single relation?

I’ll admit, I am finding it a bit difficult to follow, and your earlier screen shots weren’t very helpful because I couldn’t tell which table is which, and there was too much redaction to be able to determine which values were arrays and which weren’t.

If you’re still stuck with this, would you mind giving me temporary access to your team? I feel that if I could see all this in front of me, I could help solve your problems in seconds.
