December 8, 2016 at 10:07 am
For an existing ssrs 2008 report that is running on a ssrs 2012 report server, I believe the call from the .net application that will call the report server will look something like the following:
Since this is my first time obtaining parameter values from a call from an application, I have the following questions:
1. Does the name of the parameter need to be exactly like what is passed in the url. For example listed above, there 'schoolyear=2017'. Does the SSRS report name need to be exactly 'schoolnum' or can the name be something else?
2. How does the ssrs report know what parameter field applies to the values listed above? For example, how does the ssrs report know where 'schoolnum=341' should be applied in the report? Does having the parameter marked as hidden make a difference? Does the order of parameters listed make a difference?
3. There are the first two parameters called admin and userid that are not listed in the url? These 2 parameters have default values. Do I need to pass those 2 parameters in the url? Can you tell me why or why I would not need to pass those parameter values in the url (link)?
December 8, 2016 at 12:17 pm
I'm not sure about this particular instance, but for passing between SSRS and a SQL stored procedure the parameter names in the report need to match those in the proc. This addresses your second question as well; SSRS and SQL match parameters on the name, so it doesn't matter what order you display the parameters on the report, or if you hide them. However, as I said I'm not sure how much of this translates to your case of passing via an URL.
December 8, 2016 at 3:24 pm
You are correct that these are the exact parameter names used in a stored procedure. Do you know if a stored procedure is required for this process to occur or not?
December 9, 2016 at 1:35 pm
I'm not familiar with passing an URL from a .net application, but I think parameter names need to match whether the dataset is a query or a stored procedure (and AFAIK it can be either). I prefer to make my datasets stored procedures, because if users ask for changes to the query logic I only have to update the stored procedure without having to redeploy the report.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply