Introduction
The SAP Datasphere Multilingual Support Series is intended to provide you with useful guidance on how to utilize the new multilingual translation dashboard. The translation dashboard allows you to translate large amounts of metadata in SAP Datasphere that can be leveraged by the SAP Analytics Cloud to display the stories or dashboard in several available languages.
This article is the second in the blog post series on multilingual capabilities in SAP Datasphere.
Blog Post #1: Master Data Translations in SAP Datasphere
Blog Post #2: Meta Data Translations using the Translation dashboard in SAP Datasphere
Prerequisites
To manage translation, you must be assigned to a scoped role that inherits a template (such as DW Space Administrator), which grants the Translation privilege.
Understading the Translations Workflow
The below diagram clearly represents the activities that needs to be performed by different roles to enable, create and consume translations
Steps to setup and consume Translations
- Enable the Space for Translation
- In the Main Menu, click (Space Management) and Select a space.
- In the Overview tab, in the General Settings section, check the Enabling Translation box. Select a language as Source Language. For more information on available languages, see Supported Data Access Languages in SAP Analytics Cloud
Note:
Translation toggle cannot be disabled and the source language cannot be changed after the space is deployed.
2. Select Analytic Models to Translate in the Translation Dashboard
The user with the Translator privilege is able to launch the Translation Dashboard. All the spaces enabled with the Translation will be visible in the translation dashboard. Select the required space and you would be able to add the analytic model
- Click + (Add). The Add Objects dialog opens. Select the objects you want to translate. Click Add Objects.
- The selected Analytic Models and their dependencies are added to the tool.
Note
Only Analytic Models can be selected in the Add Objects dialog, but the dimensions and hierarchies attached to added Analytic Models are automatically selected to the Translation tool.
3. Provide Translations for required languages.
The Translator can translate the metadata using two methods:
a. Translate Metadata via XLIFF Files
You can translate large amounts of metadata with the help of XLIFF files.
Download
In the Translation tool, select at least one entity that you want to translate. Click (Download) to download the XLIFF files.
You can choose to select All Strings or Outstanding Strings while exporting the XLIFF file(s). The Outstanding Strings option is enabled only for partially translated objects. The XLIFF file is downloaded to the default location in your system.
The downloaded XLIFF file contains the source locale and the list of text that needs translation. You can use this XLIFF file in any external translation tool to generate the translated content as a separate XLIFF file per locale.
Upload
Once the translation is done, click (Upload) to open the Import Translations dialog. Click Upload Files to upload the translated XLIFF files back into the Translation tool and Click Import to upload the XLIFF files.
You can import multiple XLIFF files. Each XLIFF file contains the translated content in one language, which is automatically fetched from the language code embedded in the name of the uploaded XLIFF files. These XLIFF files can be uploaded together since they belong to one object.
Note: Name the file in the format <Analytical Model Name>_<Language (2 char)> as shown below,
b. Translate Metadata Manually
You can view the source and the translated text in the Translation tool, and add or edit the translated text in-line.
Select the object you want to translate manually and click (Edit).
The list of source text appears. Choose the Target Language and start adding the translated text in the empty field and save.
4. Consume Model with Data Access Language
Once the translations have been maintained for the Analytic Model in the Translation Dashboard in SAP Datasphere, you can see that the Analytical Model Preview displays the data in the Data Access Language.
Similarly, users can access the SAP Analytic Cloud stories built on top of this Analytic Model in one of the available Data Access Languages defined in Translation Dashboard.
Managing Translations
- Different Status of Translations per object - To see the status of the translation of an object per language, click on the object. A dialog appears with the list of translated languages and corresponding status in which the object was translated.
- Translated: Once all strings are translated completely, the status is shown as Translated.
- Not Translated: For a new object, or for objects whose translation is expired or deleted completely, the status is shown as Not Translated.
- Partially Translated: When the strings in an object are not translated completely, the status is shown as Partially Translated. Once it is translated again, the status changes back to Translated.
- Analytical Model Updated with New Columns - If the model has changed, new strings will automatically appear in the translation tool as Not Translated. Expired strings will still be available in the Translation tool. You can upload the XLIFF files even if there is a mismatch in the HTML tags between the source and target language strings.
- Deleting Translations - To delete translations, select one or more objects in the Translation tool and click (Delete). Deleting translations removes the object and attached translated strings from the Translation tool. You'll be able to add the object back to the tool, but no translation will be attached to it any longer.
Summary
Now you should be able to create and consume Translations for metadata in Analytic Models in SAP Analytic Cloud Stories.
Please like, comment or post a question!
- SAP Managed Tags:
4 Comments
