Multi-language limitations

[romain.pennes@foederis.fr]

Hello, Rollbase natively allows to work on a "multi-language" environment. To do this, you have to set the customer zone to have access to both "French" and "English" for instance and set French to be the default language (Base language). This allows the creation of multi-lang fields. You have to check the " Ce champ permet de stocker plusieurs valeurs pour les langues prises en charge ", which I believe is " This field can be used to enter multiple translations for possible languages " when using the english Rollbase edition. This allows for the creation of records in both French and English. An example of a record bellow: All of this is great, but we have found some limitations. What we have found so far: When using Client-Side AJAX APIs and Server-Side API, all functions " selectQuery ", " selectValue " etc. return the "base language" translation. As far as we know, it is in fact impossible to retrieve the other translations (additional languages) when using rollbase API functions. For this to be possible, there should probably either: Be another function like for instance "getTranslatedValue(objName, objId, fieldName, lang) ". Lang being a string like "en", "fr", "it"... Be considered that on UI (back office) should be return the language of the connected User, and on portals, should be returned the language assigned to the portal. When using template tokens (for instance " {name#text} "), the result value always is in the base language. It is also the case for textarea fields with #html property (for instance " {additional_comments#html} "). However, when using the more simple template token (" {!name} " or " {!additional_comments} "), it well retrieves the language of the connected USER on the UI, and the default language assigned to the portal on the portal. Thank you, Romain

Continue reading...