# Multi-Enum Reference – Missing enum\_name/enum\_value on records

**URL:** <https://community.appfarm.io/t/multi-enum-reference-missing-enum-name-enum-value-on-records/2285>\
**Category:** Bug reports\
**Tags:** app-data\
**Created:** [February 25, 2026, 2:40pm UTC](https://community.appfarm.io/t/multi-enum-reference-missing-enum-name-enum-value-on-records/2285 "2026-02-25T14:40:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kaspar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/kaspar/32/3073_2.png) [@Kaspar](https://community.appfarm.io/u/Kaspar)\
**Post date:** [February 25, 2026, 2:40pm UTC](https://community.appfarm.io/t/multi-enum-reference-missing-enum-name-enum-value-on-records/2285/1 "2026-02-25T14:40:36Z")

</div>

Hi, I discovered a bug when using a multi-enum property on an object class:  
Only the enum’s `_id` is accessible on the record. The `enum_name` and `enum_value` properties are not exposed, making it very difficult to use enum data in UI bindings or conditions.

**Steps to Reproduce**

1. Create an object class with a multi-enum property

2. Populate it with enum values

3. Try to access `enum_name` or `enum_value` on the stored record - only `_id` is available (see screenshot)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/e/efaf3063cf849e8ea384c63df3d8ebcd802d4e36.png)

**Expected Behavior**

Enum properties (`enum_name`, `enum_value`) should be accessible directly on the record, consistent with how single-enum references behave.

**Current Workaround**

Load the enum as a separate data source, then iterate over it and match `_id` against the stored value - but since `_id` isn’t directly accessible via data binding or conditions, this can only be done via the function editor in code (see screenshot). Note that this approach will produce the error message `Property '_id' does not exist on type 'Readonly<enum>'` in the code editor but at least it seems to work.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/7/762ba49e176fb2cc9d2a0c53295f032865f7f234.png)

This means that, e.g., iteration containers require a preceding action flow to have already run and mapped/selected the relevant enums.

This adds unnecessary complexity for what should be straightforward enum access, so would love to see it fixed 😃

---

<div class="post-metadata">

**Author:** ![rhys](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/rhys/32/1379_2.png) [@rhys](https://community.appfarm.io/u/rhys)\
**Post date:** [March 2, 2026, 8:36am UTC](https://community.appfarm.io/t/multi-enum-reference-missing-enum-name-enum-value-on-records/2285/2 "2026-03-02T08:36:04Z")

</div>

Hi Kaspar,

Would you be able to share access to me, [rhys@appfarm.io](mailto:rhys@appfarm.io) for the affected solution? This would help me to gain more insight into the use case, and try and determine a potential solution or to report this concretely as a platform improvement.

I have tried to recreate this in my own solution, but it seems like the behaviour is as expected. This is for version 135.0.22. I have tested Enums of type “string” and of type “Auto” and both behave as expected.

DevTools:

 ![Screenshot 2026-03-02 at 09.32.33](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/6/6bc2e78653b1ef14d6e5a3da2e4499b93aa2d73b.png)

Iterating through in the UI:

 ![Screenshot 2026-03-02 at 09.32.51](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/3/376a4ad18719ce9ed2596636361ec28c2b4dcacc.png)

Action logic:

 ![Screenshot 2026-03-02 at 09.33.28](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/b/b254b5fe117c9c542adab2f812d609e025b7d2a3.png)

 ![Screenshot 2026-03-02 at 09.34.48](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/f/f69e5234eee77740a77b4c9e037850ce35985672.png)

---

<div class="post-metadata">

**Author:** ![rhys](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/rhys/32/1379_2.png) [@rhys](https://community.appfarm.io/u/rhys)\
**Post date:** [March 10, 2026, 9:03am UTC](https://community.appfarm.io/t/multi-enum-reference-missing-enum-name-enum-value-on-records/2285/3 "2026-03-10T09:03:24Z")

</div>

Updating the thread for reference - this bug has been resolved after deploying to the latest Appfarm version. It seems that this was connected to a bug in the way multi-cardinality Enums were stored/represented in an earlier Appfarm version, which has now been fixed.
