Add translations to tabular reports.
You will start with a simple data model that includes the Product, Date, and Sales tables from Adventure Works. To create a star schema, you must combine the Product tables in a database view.
The dimension tables have names in several languages. Currently, each language has a separate hierarchy. The aim is to present the user with a single hierarchy that automatically displays the correct translation in Anaplan XL.
To do this, Anaplan XL uses a naming convention to choose the best translation to show the user. For example, you will have the Product Category Name, which should be translated into reports.
You can rename EnglishProductCategoryName
to Product Category Name.
This will be the default translation if no better one can be found. Next, rename SpanishProductCategoryName
> Product Category Name_es
and FrenchProductCategoryName
> Product Category Name_fr
. The extra two letters are the language code. These are standardized by ISO, so it's simple to find the correct code for any language you need.
You will do the same for the Product Subcategory Name
and Product Name
.
If you don't want users to access these columns, you can hide them in the model, and translations will still work correctly. You can also add translations to column names so that users see friendly captions when using these columns and attribute hierarchies. You do this using the standard metadata translation tools for Analysis Services.
With this done, the model appears:

You will see the translations if you turn on Use tabular culture aliases in the Anaplan XL > More > Manage Aliases screen. Below are before-and-after screenshots. Both grids use the same hierarchy:
