Recently I was asked to create a multilingual prompt label. Stijn Gabriels pointed me in the right direction.
First I created a dummy table in the .RPD with a single date column:
Next I put in the presentation catalog:
In my translation table I added the column and it's translations:
Based on this column I created a prompt with no label text:
Now in the dashboard it's available in Dutch:
In English:
In French:
You can use the presentation variable for your filtering.
Till Next Time
4 comments:
Hi John
We have a scenario where the user language selection is done from the FMW interface and the parameter is passed to OBIEE. Based on this, reports in OBIEE should be displayed in the respective language exposed on ADF interface.
Any thoughts/ inputs?
Regards
S.
@SparjanK,
Does the parameter fill the WEBLANGUAGE system variable?
Regards
John
Hi John,
No. We are looking on implementing this using the XML files (not by session/system variables).
How to syncrhonize OBIEE and FMW so they both show the same language? Can FMW determine the Locale and pass it to OBIEE?
We are trying to determine the language based on the user’s browser settings (from http request) and we need to ensure it’s consistent between OBIEE and FMW. We can either have FMW pass the locale to OBIEE, OR if that is not possible, the alternative is to have both FMW and OBIEE determine the language based on the locale passed in the HTTP request.
Do you think using the session/system variables approach will be good in this scenario? Awaiting your inputs.
Regards
S.
@SparjanK,
I would go for passing the FMW variable to OBIEE. That way you know for sure there are no interpretation differences.
regards
john
Post a Comment