Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
We upgraded to Jan 2020 version on our Development server yesterday and found a problem with how reporting services is passing the multi-value parameter values in ad-hoc query.
A simple explanation of what is happening
1. We have a report with multi-value parameter name @School
2. There is a dataset with an ad-hoc query which has variable name @SchoolYear and using the values coming from @School parameter
DECLARE @SchoolYear INT
SET @SchoolYear = MAX(SCHOOL_YEAR) FROM DIM_SCHOOL
SELECT *
FROM DIM_SCHOOL
WHERE SCHOOL_ID IN (@School) --parameter
The report is failing when I pass more than one values for @School parameter because reporting services is replacing @SchoolYear variable with the @School values.
DECLARE N'496',N'375'Year INT
SET N'496',N'375'Year = MAX(SCHOOL_YEAR) FROM DIM_SCHOOL
The same report works fine in another server with Mar 2018 PBI Report Server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.