Data localization scenario example

docs
, ,
1

I have the Country table (containing Name and Code columns) and I want users to be able to localize country names by themselves.

  1. Right-click on the Country entity > Actions and select option Create Localization child entity...:
    image

  2. In the next dialog select all fields that you need to be translated and confirm OK:
    image

  3. New Country_l10n entity, relationships and deployment scripts are created for you (as a child of the Country entity). Confirm Yes.

    image
    image1040×158 9.65 KB

    If you don’t like the caption Country Localization generated for this new entity, change it (e.g. “Translation”).

  4. In the Country data structure add Country_l10n as a child (right-click on the entity New > Entity). Use the “_all” relation, if you want all languages to be added.
    Create the screen section (Country_l10n > Actions > Create Screen Section...) and select refLanguageId and Name to be shown in the form.
    Insert this new screen section into the Country screen as a child (by using the SplitPanel widget).

  5. Change LookupCountry data structure used for the selection of countries in screen sections so it will be localized:

  • Set IsLocalized=True in the lookup data structure
  • Add the new child entity Country_l10n with AllFields=False and RelationType=LeftJoin.
    image
    image
  1. Now users can add translations for every Name in the list.
    In forms the data will be used according to the user or application language settings.
    When there is no translation, the original value is used.
    image