SQL Reporting Services keeps a copy of every report rendered in its cache. Of course this is quite a performance boost when a lot of users request the same report over and over again. But in our case this cache turned against us. We have an ASP.NET app whose reports are included in the app as a bunch of links to the reporting server. The page assembles the URL with the parameters (more on that later) and redirects the user to the report. Every time the user opened a report she was confronted with the previous version rendered. Based on the previous parameters. Clicking the the RS toolbar's refresh button (NOT the browser's refresh button) led to the intended report.
You can configure the caching of reports in great detail. It's under the execution tab in the report manager.
But there is a little quirk in this. Even when you set the report to Render this report with the most recent data, the user is (in our scenario) still confronted with a cached copy. This is either a bug or a misunderstanding between me and RS, I've seen others. What helped me here was using the rs:ClearSession parameter. In our app this is now the base URL for a report.
protected string reportServer
{
get
{
return System.Configuration.ConfigurationSettings.AppSettings["ReportServer"] + "{0}&rs:Parameters=false&rs:Command=Render&rs:ClearSession=true";
}
}
The report name and parameters go into the {0}
To be continued.