The report execution xnf441454bs2oh45hqvrkd45 has expired or cannot be found. (rsExecutionNotFound)
The problem was the parameter: I was using a text field to pass through information for the parameter, and this textual information could include an Ampersand (&).
This is obviously a reserved character, so requires escaping.
To do this, we must utilise SSRS's commands REPLACE and ESCAPE in the custom action. The easiest way to explain this is in this example:
="javascript:void window.open('" & Globals!ReportServerUrl & "/ReportServer/Pages/ReportViewer.aspx?%2fPhonebook+Reports%2fDepartment&department=" +Replace(Fields!Team.Value,"&","' + escape('&') + '") & "&location="+Replace(Fields!Location.Value,"&","' + escape('&') + '") & "&rs:Command=Render=','_blank','')"
Using this format to build the link, I can now open "drill through" reports with a parameter that contains an ampersand, and no longer get the "report execution" error above. Nice.
Festina Limited Edition Chrono Bike 2015 Men’s Quartz Watch with Brown Dial F16883/1 |
Click here for a list of the best selling Festina watches this week.
No comments:
Post a Comment