Skip to end of metadata
Go to start of metadata

Known Issues


As of Lumira 2.1 the Designer uses the following URL parameter when starting an app via Execute Locally (not for Execute on BIP):


This will have the effect that locale settings will not be correctly set, only EN-US will be taken as it is the default.

Simple workaround: after choosing execute locally remove the above parameter from the URL and refresh in the browser whenever you need to load the changed application again.

Important: this parameter is not used on the platform in BI launchpad or OpenDoc, therefore this symptom will not occur on the platform.


The date picker e.g. in the variable dialog did not show the correct format. This is fixed with Lumira 2.3 SP 2. (Jul 3rd: Updated to SP 2)

2465894 - SAP Lumira 2.x - Release Schedule

3. Translation Management Tool bug

After Saving As (in the Designer) of an application inside a LUMX the translation management tool does not show the duplicated texts.

This is fixed at least with translation management tool 4.2 SP 5 Patch 2.

 4. Designer Save As

2809528 - Translation Management Tool does not show any translations after "Document -> Save As" for a translated BIP document

5. Chrome Setting without country => default texts in Lumira

In case your chrome language setting does not show a country this result in an HTTP accept-language header where the country is missing e.g. de instead de-DE. The Lumira addon will show the default application texts then.


Lumira Applications can be have three types of multilingual text source categories:


– Backend : business data coming from Data Sources. Guarantee that objects are language dependents and data was translated in the source system. This data can be represented by master data or metadata. Regarding fallback language - first it will try with the current PVL country specific code e.g. for German (Austria) that’s 1G. If not supported, it will fallback to the simple language code e.g. for German (Austria) that’s DE. And if that’s still not supported it will fallback to EN.


– User Specified Translation : represented by Technical Component TEXT_POOL, which creates the file. With the support of Translation Management Tool  (TMT), texts can be translated to several languages and strings exported to the BIP system repository. The fallback language is to application developers language, which is EN.


– Product Texts : these are default Designer texts like Menu options, Navigation Panel header, Menu for Charts…


Bellow settings can be defined in the BI Launch Pad in order to fulfill user requirements (unchecked box means setting does not interfere in the text source category).


User Specified


Product Text

Preferences -> Preferred Viewing Locale (PVL)

  • can be Browser Locale or a fixed specific Locale


OLAP Connections -> Save Language

  • a language defined in the OLAP connection has priority over PVL. Check KBA 2193157
  • in case it is needed to fetch user settings from BW, check KBA 2377125
    EW: check the troubleshooting document attached to the note.
    Note that the backend user settings are not considered if the Save Language Flag in the OLAP connection is checked. Furthermore the backend settings only affect data coming from backend like crosstab or filter data. It does not affect UI elements like a date picker e.g.


(green star) Each of the three Texts Source Categories can have error/warning messages during Application Runtime. The messages locale respect the text categories locale.

(blue star) Locale can also be configured via OpenDocument URL parameter. Check KBAs 23554112293763.

      &LANGUAGE=xx&COUNTRY=xx is the recommended way for the language selection.

      "Allow Language to be set as an OpenDocument" should be activated in the CMC Lumira Server Settings.


In order to have the BI Launch Pad settings applied to Lumira applications, select BI Platform User Settings‘ in the Lumira Client Preferences.


The format for numbers, dates and times varies according to the defined Locale.

(error) Interval Filters : Setting a interval variable via script is only possible with setVariableValueExt - but this is language dependent. If the application is intended to be used by a multi-lingual group of users, this method can bring system limitations.

Known issues

  1. Right menu lumx file has no dutch translation in right mouse menu
  2. in IE the language setting of NW PORTAL is not respected for french language. - fixed in 2.2 release
  3. Lumira shows comma for decimal operator for turkish language.



If you test in the Designer do not choose the red setting. Otherwise the Designer will overwrite the browser language settings with these URL parameters: &LANGUAGE=en&COUNTRY=US

Browser Locale determine language specifics

A typical use case for English language but European date/time formats using the UK locale instead of English-US. The browser locale (PVL) determines all translated texts, the backend texts from the data source (e.g. "Flight Date") and product texts from the Lumira UI element (e.g. "Show Filterbar").

BIP user locale determine language specifics

Another typical scenario where the user locale configured on BIP determines all translated texts and formats.

Browser Locale as well as OLAP connection determine language specifics

An untypical mixed language scenario with a language specified in the OLAP connection of the BIP (German in this case) and the EN-UK browser locale. As you can see backend texts (yellow) are determined by the OLAP conection setting. All backend texts (green) are determined by the browser locale.

  • No labels