When it comes to column default alias and description I found a post: https://forum.reportserver.net/viewtopic.php?id=605
Maybe it’s a good direction to solve problem but I rather prefer saving column alisas and description in database because I will have a lot of different reports with two languages.
I wonder now how can I adjust parameter name and description according to language? Now this seems to be a problem. In the worst case I would have to create two reports, one for each language…
nevertheless, you should be able to create a script datasource that depending on the language selects the right columns (mycolumn_de, mycolumn_en, mycolumn_pl, etc). Similar as here: https://forum.reportserver.net/viewtopic.php?pid=2424#p2424
Then use this script datasource as a metadata datasource in your report.
This only works for column names and descriptions, not for parameters. For parameters, we have the ticket I mentioned above.
Hi Eduardo,
I understand.
Is it possible if this ticket is done in next version 3.0.8?
I hope you issue next version very soon because I am still working on a preview version of 3.0.8
Till that time I will adapt my columns depending on current languages.
Is there or will be any possibility in future:
to have constant parameter possible to use in query (query for data and for metadata) which says which language is chosen (locale) - sth like ${CURR_LOCALE}?
use any parameter in metadata query wrapper? (like in query for data I can use my defined parameters)?
I think these two features will help users a lot and simplify a lot of questions.
I raised 3 tickets for related multilanguage features:
RS-3484: Multilanguage Report Metadata
RS-3485: Multilanguage Datasource Parameter
RS-3486: Multilanguage Parameter
I also raised:
RS-3487: Make locale available to query wrapper
I am not sure if they will make it to 3.0.8 , but these tickets are open they are interesting feature requests. I will update here when I have more information.
I just wanted to let you know: we are currently working on making some standard parameters available to all queries (metadata query, normal query, query wrappers, etc). This includes locale, current username, etc. The default parameters will be included in a menu, so they will be very easy to select.
When this is finished, you will be able to easily create a metadata query that depends on locale:
select * from mytable where locale = ${_RS_locale} or similar. I will update here when I have more information.
Hi Eduardo,
Just for your information, nowadays in my version I can use in query ${_RS_LOCALE} and it works
Only in windows of administration Execute of Metadata Query doesn’t work but when I open Execution View it works as I expected (get English aliases of coulmn from metadata query)
please test the following in your metadata datasource:
select * from mytable where locale = ${_RS_LOCALE}
This should already work. The only missing part is showing a list to the user in the GUI with all available default parameters But if you write the parameter directly into the query, it should work. Please confirm.
With this, you can already translate default alias and description
Regarding the other ticket, yes, we will take a look, it seems related as well.
One more thing
_RS_REPORT_KEY
This one doesn’t work well.
If I open base report I expect base report key. If I open variant I expect variant report key.
Unfortunately this doesn’t work. _RS_REPORT_ID and _RS_REPORT_NAME work as expected, so only _RS_REPORT_KEY is a problem.
What’s interesting in Administration, if I click button Execute on data query I see the key of base report, but in Execution View this column value is empty.
Could you check why _RS_REPORT_KEY doesn’t work?