Has anyone else encountered this problem before? If so, is it documented anywhere?
I wrote a report that used a stored procedure ("sproc") in the core dataset. The sproc used parameters, which I defined in the report. The dataset worked properly on the Data tab of the report. But whenever I rendered the report, no matter which values I set the report parameters to, I always saw the same data in every object that used the core dataset.
I discovered that the sproc's parameters were defined with default values on SQL Server 2005. Reporting Services was not using the report parameter values; rather, it always used the default values as defined by the sproc!
After the default values were removed from the sproc, the dataset started using the report parameters properly on the rendered report.
Correct me if I'm wrong, but as far as I'm concerned, this is a bug in Reporting Services 2005. Even if it's documented behavior, it's counterintuitive and ought to be fixed.
I wrote a report that used a stored procedure ("sproc") in the core dataset. The sproc used parameters, which I defined in the report. The dataset worked properly on the Data tab of the report. But whenever I rendered the report, no matter which values I set the report parameters to, I always saw the same data in every object that used the core dataset.
I discovered that the sproc's parameters were defined with default values on SQL Server 2005. Reporting Services was not using the report parameter values; rather, it always used the default values as defined by the sproc!
After the default values were removed from the sproc, the dataset started using the report parameters properly on the rendered report.
Correct me if I'm wrong, but as far as I'm concerned, this is a bug in Reporting Services 2005. Even if it's documented behavior, it's counterintuitive and ought to be fixed.