I am passing in two parameters through a URL to my report. They limit the selections in one dataset that is used to populate a drop down list of report parameters (in this case 'Regions'). The url parameters are Region and Role. If the role is a manager, they can see a larger selection of regions in the dropdown list, if they are not a manager, they see only their region as an option in the dropdown. Please don't be confused by the fact that the dropdown is showing a selection of regions, while at the same time the URL is passing in a 'Region' parameter -- there is a reason for this but it doesn't relate to this issue.
The URL parameters are used in a report dataset (running a stored procedure) that expects the two parameters. The parameters are used nowhere else in the report. Under the report parameters definition tab, I have the url parameters at the top of the list (as I understand it, this forces the report to evaluate them first). When I run the stored procedure in SSMS, it functions as expected -- both when I pass in 'Manager' or 'SalesRep' as role. When I pass in 'Manager' in the url, it functions as expected (that is, the drop down shows all the expected selections). When I pass in 'SalesRep' in the url, the drop down list is empty -- which to me suggests that the sproc is not returning the filtered dataset.
Again, running the stored procedure in SSMS with both versions of parameters returns the results I expect. Only when they are sent in via the url do I get 'wrong' results.
When I preview the report in BIDS, manually typing in various values for the parameters that would otherwise be passed in in the URL, the report runs as I expect. Also, as I mentioned above, in SMSS the sproc runs fine.
Any thoughts anyone? many thanks. David