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
-
Create an object class with a multi-enum property
-
Populate it with enum values
-
Try to access
enum_nameorenum_valueon the stored record - only_idis available (see screenshot)
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.
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 
