Tuesday, January 17, 2012 7:46 PM
We have SharePoint 2010 with ReportServices Integrate with SSRS 2008 R2. Everything seems to work fine except when we try to select a default value of query based parameters. The drop down in Manage Paramaters is always empty. These reports parameters, when supplied from a query, worked in 2007 but do not in our production or development 2010 instances. In either case, the report runs and the parameter values fill out properly when the report is run, just not when managing the parameters.
Please help!! We can't really even find proof that this feature works in 2010 at all.
Thursday, January 19, 2012 8:59 AM
1. Please check the “Available Values” section in the parameters dialog, make sure you select the “Specify values” or “Get values from a query” here.
2. If you have check the above choice, please try to publish the new report to SharePoint Document library, and share you result;
TechNet Community Support
Thursday, January 19, 2012 10:25 PM
Thank you for the reply. 1#2 is how we do it. If the parameter has a specific list of available values, the drop down works. If it is a query it does not (the drop down shows with now values)
This behavior occurs in production and development instances so it is reproducible across multiple deployments for us.
Thank you again for any attention you give this issue.
Friday, January 27, 2012 4:45 PM
As further information, we also did a SQL Trace and SharePoint is NOT running the value query to populate the possible values in the manage parameters dialog.
We have not been able to make this work in any 2010 SharePoint server has this functionality been broken in 2010? It works readily in 2007.
Monday, April 16, 2012 12:12 PM
We have the same issue and we have tried everything mentioned above.
What we are doing is creating additional SSRS reports with their own default parameter values and deploying them. But this is NOT a workaround since we have over 250 reports!
Has anyone found a solution workable solution?
Monday, April 16, 2012 3:54 PM
While working with a client that experienced this issue we opened a support ticket with Microsoft and they confirmed that this is a known bug within SQL Server 2008 R2 and is to be addressed with the release of SQL Server 2008 R2 SP2 (unknown release date). Additionally this bug is fixed with the new release of SQL Sever 2012.
which are similar thread to this but may have additional details.