Regarding localisation vs enums. A workaroun...

(Christian Farley) #1

Regarding localisation vs enums.

A workaround that had been proposed in the past was to add all languages values in the enum list, and then filter on language using a valid_if clause. e.g Yes No Oui Non Then if [language] = “English” > show only english terms.

But this means that the values saved are also multilingual, which means that we must create more complex expressions to deal with each language permutation.

What would be needed is a way to store a generic value, then show variable enum values. For instance: Yes = 1, No = 0. What would be saved in the row would be only 1 or 0, but “Yes” or “No” (or whichever other value based on language) is what would be displayed on the enum buttons.

Note: we know that there is a yes/no column type. This is just a simple example. But the use case is also applicable to random terms.

Is there any work in progress on Appsheet to help better support multilingual values on enum columns?

(Praveen Seshadri (AppSheet)) #2

Not at the moment, but it is an important and needed feature for a multi-lingual app. Could you please add the request to - Login - AppSheet

Thanks! Login - AppSheet

(Christian Farley) #3

Will do. Thx