Passing non-English parameters to reporting services via URL access
Few weeks ago I faced a problem when I was using SQL Server Reporting Services to gen
August 12, 2005
Few weeks ago I faced a problem when I was using SQL Server Reporting Services to generate a report in which all parameters' values in Arabic.
The problem appeared when I used this report through URL access, and passed the parameters' values throug URL. I did a simple report to reproduce the problem. Let's say I have a report like this
http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
0.25cm
2.5cm
textbox1
0.63492cm
6.75cm
0.25cm
true
=Parameters!CustomerName.Value
1.5cm
2.5cm
16cm
2.5cm
true
29.7cm
true
21cm
573728dc-7d8a-4652-8a69-3a9c1a55887b
2.5cm
String
true
CustomerName
en-US
When you call this report through URL access and pass the parameter CustomerName like this&rs:Command=Render&rc:parameters=false&CustomerName=???You note that the report doesn't recognize the parameter value passed. The report considers it as empty string. To avoid this I found in Service Pack 2 documentation that you need to add this parameter rs:ParameterLanguage= so in my case I should add rs:ParameterLanguage=ar-EGI tried this but It didn't solve the problem. I tried another way and it solved my case, I URL encoded my parameters values before passing them to the report.If you are using web application and you want to show a report. You can use Server.URLEncode("").If you are using windows application, you need to reference System.Web.dll assembly and use HttpUtility.UrlEncode(" (it's static/shared method).I hope this help who may face the same probelm.http://blogs.msdn.com/mohamed_sharafs_blog/
About the Author
You May Also Like