SQL Server Home
Multi-value cascading parameters list refresh problem
4/7/2009 11:47:28 PM
User(s) can reproduce this bug
forgive me, i am not an english speaker.
i have 3 parameters, Country, State, City and all are multi-valued. State is depend on Country, City is depend on State. Default value is set to all avaliable values [Select All].
This issue is if user changes the Country value(1st parameter) ,and cascading refresh State (2nd parameter), the City(3rd parameter) list will not be refreshed.
my real report is using Reporting Services 2008 querying from a SSAS cube, for simplicity, i use SQL Server db as demo. This issue is also exist in my cube report.
i also tried the same report in Reporting Services 2005 without any SP, all the parameters and their default values work fine.
SQL Server 2008 - Enterprise Edition
Windows 2003 Enterprise
Operating System Language
Steps to Reproduce
1. attach myNorthwind database and open the attached report.
2. When the report loads for the first time, all the default values for all the parameters are selected, it works fine.
3. change Country parameter, for example:"UK", note State parameter list is refreshed correctly. At this time, City parameter list should be refresed and contain only cities that belong to "OH", sadly, it contains all cities.
Cascading parameter not refreshed, when intermediate multi-value parameter list refreshed due to 1st parameter change.
Cascading parameter shoud be refreshed, when intermediate multi-value parameter list refreshed due to 1st parameter change.
to post a comment.
Please enter a comment.
on 6/25/2009 at 4:45 PM
(RS 2008) I see this issue even for the 2 parameters. I have a parent parameter having the available values with multi-select option, the second parameter is defined as (Parameters!Parent.Count). Now when I preview the report, for the initial selection the second parameter shows up the right values but for the subsequent selection it still shows up the initial value :(. Is this fixed as a part of CU#5? Please let me know.
on 4/8/2009 at 8:57 AM
Thank you for reporting this issue. The fix will be available in the next cumulative update, i.e. CU#5 that is expected to be released in mid May. CU#5 will be a publicly available download.
If you have to get it earlier, you can call/contact Microsoft Support (CSS) directly today (http://support.microsoft.com/contactus/cu_sc_more_master?ws=support#tab1), open an incident and specifically ask to get access to a on-demand QFE for this issue that we made available a few days ago. When calling CSS about the on-demand QFE, please refer to SQL Server QFE ID 291168, hotfix build 10.00.1799, hotfix ids 376783 (x86), 376782 (x64), 376781 (ia64).
Reporting Services Team.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft