February 1, 2012 at 10:46 am
In some reports that have a multi value option, when this parameters is passed to another dataset it appears to be changing the T-SQL. From SQL Trace it changing the parameter name and any other reference to it with the multi select string.
E.g.
Declare @TeamName Varchar(1000) = '-1'
is now
Declare N''Acute OT - Assist Pract'',N''Acute OT - Assistant'' Varchar(1000) = '-1'
Has anybody else had this problem and who do you resolve it?
February 1, 2012 at 11:16 am
Can you elaborate on what you mean by "passed to another dataset"
Are you talking about passing to a stored procedure, a report action calling another report....?
February 2, 2012 at 2:43 am
A multi select parameter has its values returned from a sql statement. On a subsequent parameter's dataset query it passes the selected values from the previous multi select parameter as a parameter to the second parameters dataset query.
In SQLTrace the second query the parameter name in the query is replaced by the concatenated string of values form the first parameter..
February 2, 2012 at 7:04 am
Are you using a JOIN of the original parameter data to feed your second dataset?
JOIN(Parameter.Value,", ")
Is your second dataset being fed by an inline query of stored procedure. If you are using a stored procedure you need to build a table value function to take the comma delimited data and split it.
February 2, 2012 at 10:21 am
Thanks I have changed the report to pass the parameter using the Join function and then using a sql function within the query to use the data.
This is now working.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply