# Static list field (enum field) in glide database

**URL:** <https://community.glideapps.com/t/static-list-field-enum-field-in-glide-database/53218>\
**Category:** Feature Requests\
**Created:** [November 3, 2022, 12:47pm UTC](https://community.glideapps.com/t/static-list-field-enum-field-in-glide-database/53218 "2022-11-03T12:47:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dilberryhoundog](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@dilberryhoundog](https://community.glideapps.com/u/dilberryhoundog)\
**Post date:** [November 3, 2022, 12:47pm UTC](https://community.glideapps.com/t/static-list-field-enum-field-in-glide-database/53218/1 "2022-11-03T12:47:08Z")

</div>

Most databases / spreadsheets have some kind of field that you can pre fill a few options, which is called an enum field (or in non computing terms a static list).  
An example of this type of field is Airtable’s status field or apple numbers “Pop-Up” field.

You simply write some options into the field when setting it up. Then when entering the data into the field only these specific options are available to enter.

A common example is… todo, in progress, on hold & done.

I think an enum field in Glide databases would be amazing. It would prevent having to setup a relation to a “utility” table (2 extra fields) and a lookup (a 3rd field) just to reference a predetermined list of (static) options.

---

<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:** [November 3, 2022, 1:14pm UTC](https://community.glideapps.com/t/static-list-field-enum-field-in-glide-database/53218/2 "2022-11-03T13:14:50Z")

</div>

I think you might be looking for the Choice Component?

> **[Choice Component](https://www.glideapps.com/docs/reference/app-components/choice-component)**
>
> Pick and submit options from a list.

---

<div class="post-metadata">

**Author:** ![dilberryhoundog](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@dilberryhoundog](https://community.glideapps.com/u/dilberryhoundog)\
**Post date:** [November 7, 2022, 11:18am UTC](https://community.glideapps.com/t/static-list-field-enum-field-in-glide-database/53218/3 "2022-11-07T11:18:18Z")

</div>

Yeah I looked and I did find what you are referring to. If a relation field is used by the choice component for its values, it will write to the text field that the relation uses. Using a relation field like this does remove some complexity.  
However I find a significant portion of my “static choice” fields are multiple choice, whereby the choice component won’t read ‘list type’ relation fields. This is where a new database field that enables predetermined static choices would be a good idea. It will also simplify single select choice fields as well because you won’t have to setup a relation to a “utility” table.