How to correctly implement language variable choices on record producer

sravanku888
Tera Contributor

I have a Record Producer with a 'Select Box' variable named 'language'. Its choices are currently static language names like 'Dutch', 'Spanish', 'French', 'Portuguese'. My goal is for these choice labels to display in the user's chosen language (e.g., if a user's profile language is German, 'Dutch' should appear as 'Niederländisch'). I've tried changing my user profile language and then updating the choices, but this just overwrites the original choice label with the new language's label, making it static for everyone regardless of their language setting. What's the correct approach to achieve dynamic translation of these language names?

6 REPLIES 6

James Chun
Kilo Patron

Hi @sravanku888,

 

That should be the correct way to set the labels for different languages.

Can you confirm if 'Translated Name/Field' record is created in the [sys_update_xml] table?

e.g.

JamesChun_0-1748313122706.png

JamesChun_1-1748313171020.png

JamesChun_2-1748313230688.png

But I think what happens is that when you update the label of the system's default language, it overwrites the label for all the different languages. So, if your default language is English, make sure you modify the label of English first and move on to the rest.

 

Cheers

 

The challenge I'm facing is that the choice values themselves are not consistently translating to Spanish. For instance, if I have a choice "Computer" in English, and I've provided the Spanish translation "Computadora", it only displays in Spanish if the user's language is explicitly set to either English or Spanish. If the language is set to anything else (or perhaps defaults to English before switching), it might not show the Spanish translation.

What's working correctly:

The labels of the form variables themselves are translating perfectly to Spanish.
What's not working:

The actual choice values within the select box variable are not changing to Spanish as expected, especially when populated from another table.

So what you are saying is that the 'value' (not the label) of the choices are not translated?

If so, this is the expected behaviour. The 'value' of the choices must remain consistent across different translations, you are not translating the 'value' but only the 'label'.

The challenge I'm facing is that the choice values themselves are not consistently translating to Spanish. For instance, if I have a choice "Computer" in English, and I've provided the Spanish translation "Computadora", it only displays in Spanish if the user's language is explicitly set to either English or Spanish. If the language is set to anything else (or perhaps defaults to English before switching), it might not show the Spanish translation.