The prompt concerns Measures so prompt question should be something like:
ENG: Choose Measure
FRE: Choisir Mesurer
And values should be something like
ENG: Quantity, Revenue
FRE: Quantité, Revenu
And this is where the hard part comes in:
Below this question there is (obviously) a reference to a table;
So If ENG user chooses Quantity.
The object returns SQL code like: MEASURETABEL.QTY
In IDT 4.0 I see in the LOV/Parameter the possibility to add more columns to your LOV-list but it’s impossible to set-up the request like above
so attach a TECHNICAL column, to the object and a FRE column to the FRE users and a ENG column to the ENG users.
You can (automatically it does) show ALL 3 columns to your users but that’s not a NICE solutions…,
UPDATE: . And I’m still strubling with the PromptQuestion in 2 languages.
And I’m also strubling with displaying the right UserResponse in the report, cause now it’s displaying the TECH name and I want the ENG or FRE name… (without doing if-then-else AGAIN)
What version are you on ? Did you try Translation Manager Tool ? Using this tool labels/headings/messages can be converted to a target language from a source language. No need of introducing new measure(s) for each different language.
Like the pre-fix in the subject mentioned, I’m in SAP BI 4.0 (SP04 to be exactly)
We use the TMT , but with this request it’s a little bit flaky… cause the @Prompt is in a object and not defined at report level, so TMT doesn’t see it when you import the report.
Further if you try to translate the UNX (blx to be precise) with the TMT you only get the possibility to translate the object name and not the details of the prompt defined… as far as I’ve seen.
I’d hoped with the possibility to add columns to your predefined LOV list in IDT 4.0 you would be able to fiddle around with those extra columns(example, attach a column to a certain LOCALE and then with some extra parameters and GetLocalized present the right column to the right group of users)
But this doesn’t seem to be the case… Actually if I look at the LOV possibility to add columns right now I don’t know why it’s there cause you can do noting with it (the only thing is that you can preset more info structured to your LOV)
What I believe is you need to have data stored in database in different language.
My company’s product is being used in more than 25 languages. We have many locale specific tables wherein data for every locale is stored identified by column java_locale.
So in each LOv query, if it uses locale specific tables, we filter java_locale column by @variable(Preferred_viewing_locale). So you will see only those values as per your preferred locale. And as you mentioned we get the locale specific prompt name using TMT.
(BOB member since 2004-11-10)
(BOB member since 2004-06-06)
(BOB member since 2008-05-26)