I got little confused with your reply to Evita, you are trying to implement the localisaiton of filtering option. It means that,
When you have for ex, if you have japanese locale set. The column should be available filtering the data based on japanese values in the tuple of the report definition? Is it? If yes, we should understand that the report definition returns values from database which was persisted earlier/during the process of application either by user input or OOTB enteries.
These values are stored as literal phrase. Thus, How you can have localised text of Japanese to filter the option available on English text?
Secondly, are you getting any error in logs or screen during filtering of localised text by some implementation at your end?
If you are getting weired(like ¿¿¿¿) characters instead of localised values. I would asked to check the character set of the database.
As i said earlier, we store english values in column. These values localized on section through field values. But when we try to filter them on section and typing russian string, we unable to filter results, because in clipboard this values stored in english version.
So the idea was to get russian values in RD through function alias. This way we can filter because this values will be stored in russian version in clipboard.
Posted: 5 years ago
Posted: 15 Feb 2017 7:23 EST
Shohaib Ahmed N (SHOAIBAHMED)
in the column format use "pzGetLocalizedValue" for each columns in Report definition this will fetch the localized values, you can create the field values so that based on the locale language the report définitions colum text displays in the locale language,