Ref vs Enum while using "Other" value

[Caden_Davis]

Hello!

I need some help with determining which Column Type/configuration to use in the case below:

I have a column/form field that looks into a read only reference data source for a list of IDs, Names, and group IDs.

I am filtering the records by the group IDs based on a previous selection in the form. (It shows the user the label of the record (Name) and saves the key (ID) in the column which is what I’m looking for)

I need the option to let the user select an “Other” value that doesn’t exist in the reference data.

Right now, I have the column type set to “Ref” and I’m using the “Suggested values” to do the filtering of the reference data.

I tried to change the column type to “Enum” and use the “Allow other values” feature, but it displays the key to the user instead of the label.

[Aurelien]

Hi @Caden_Davis

Ref type is correct, as long it is to the table, or a slice that allows Adds in the update mode.
You may want to use the Valid_If field instead of Suggested_Value.
This way, the new data entered by the user will be a part of the Ref data, assuming that’s what you want.

This is an example with a slice with Adds_Only option

Now, in the table, the column that will be completed by my user, with Type Ref, refers to the source table that allows Adds:

The expression in the Valid_If expression:

What it gives for the user:

[Caden_Davis · Accepted solution]

@Aurelien Thanks for your reply!

The reference table is read only as the data originates from a SQL database and should only include the original records and not anything the user would add.

I was actually able to add the static record through SQL in order to bring it in so I think I’m good here.