# \[solved\] Computed Fields and Collections

**URL:** <https://community.glideapps.com/t/solved-computed-fields-and-collections/67213>\
**Category:** Ask for Help\
**Created:** [October 23, 2023, 11:32am UTC](https://community.glideapps.com/t/solved-computed-fields-and-collections/67213 "2023-10-23T11:32:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![DirkR](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dirkr/32/64750_2.png) [@DirkR](https://community.glideapps.com/u/DirkR)\
**Post date:** [October 23, 2023, 11:32am UTC](https://community.glideapps.com/t/solved-computed-fields-and-collections/67213/1 "2023-10-23T11:32:11Z")

</div>

It would be great if I could use computed fields in collections. At the moment, computed fields could not be shown in collections like tables nor can they be used to sort our group tables.

Kind regards,  
Dirk

---

<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:** [October 23, 2023, 11:47am UTC](https://community.glideapps.com/t/solved-computed-fields-and-collections/67213/2 "2023-10-23T11:47:58Z")

</div>

> [@DirkR](#):
>
> At the moment, computed fields could not be shown in collections like tables nor can they be used to sort our group tables.

Yes they can. Could you provide an example where you couldn’t?

There are some limitations when it comes to computed columns with Big Tables, but certainly none when it comes to regular tables.

---

<div class="post-metadata">

**Author:** ![DirkR](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dirkr/32/64750_2.png) [@DirkR](https://community.glideapps.com/u/DirkR)\
**Post date:** [October 23, 2023, 12:04pm UTC](https://community.glideapps.com/t/solved-computed-fields-and-collections/67213/3 "2023-10-23T12:04:43Z")

</div>

Hey Darren, thanks for your reply. I have a relation Field in one of my Tables which shows the correct value for that relation in the Data-View. But I am unable to show this field when setting up a collection for that table. The field is not in the list. Is it an error?

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/f/bffc0f7e0603a3dbef9b3cfb90f69b73e63d4091.png)  
Table in Data-View

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/9/f907a6913c11b504caa6e4bd89fd7fdcd93c360f.png)  
Field not in List in Layout-View for collection

Kind regards,  
Dirk

---

<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:** [October 23, 2023, 12:47pm UTC](https://community.glideapps.com/t/solved-computed-fields-and-collections/67213/4 "2023-10-23T12:47:37Z")

</div>

A relation just establishes a link between one row and one or many other rows.  
It can be used as the _source_ of a Collection, but it cannot be used in a component that expects a single value - such as the Title or Description in a Collection.

If you want to use a specific value from the row (or rows) that the relation links to, then you need to use a Lookup (single relation) or Joined List (multiple relation) to fetch that value first.

---

<div class="post-metadata">

**Author:** ![DirkR](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dirkr/32/64750_2.png) [@DirkR](https://community.glideapps.com/u/DirkR)\
**Post date:** [October 23, 2023, 12:53pm UTC](https://community.glideapps.com/t/solved-computed-fields-and-collections/67213/5 "2023-10-23T12:53:48Z")

</div>

Okay, yes - that works. Thanks a lot!