I am having a problem with cascading parameters. The 1st time you make a selection the dependent parameters update correctly. If you select a new value from the 1st parameter, the 2nd parameter updates as expected, but the 3rd one does not update. The parameter values are still based on the selection from the 1st time.Is there something that can be done to work around this?

Which version of reporting service are you using? It is a known issue in RS 2008 and it is going to be fixed in a future Cumlative Update.This posting is provided "AS IS" with no warranties, and confers no rights.

Which version of reporting service are you using? It is a known issue in RS 2008 and it is going to be fixed in a future Cumlative Update.This posting is provided "AS IS" with no warranties, and confers no rights.

Which version of reporting service are you using? It is a known issue in RS 2008 and it is going to be fixed in a future Cumlative Update.This posting is provided "AS IS" with no warranties, and confers no rights.

SSRS 2008. Is there a release date? Also, is there anyway to get it sooner?

It will be in CU#5 but if you need it sooner, 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 weeks 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).Please refer to this link below for more details about this fix:https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=431251&wa=wsignin1.0Let me know if this is the fix you needed. This posting is provided "AS IS" with no warranties, and confers no rights.

It will be in CU#5 but if you need it sooner, 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 weeks 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).Please refer to this link below for more details about this fix:https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=431251&wa=wsignin1.0Let me know if this is the fix you needed. This posting is provided "AS IS" with no warranties, and confers no rights.

It will be in CU#5 but if you need it sooner, 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 weeks 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).Please refer to this link below for more details about this fix:https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=431251&wa=wsignin1.0Let me know if this is the fix you needed. This posting is provided "AS IS" with no warranties, and confers no rights.

It is the fix I need and I have contacted Support. They didn't seem to know what I was talking about and referred me to IT. They could not help me either. What does QFE stand for?

It is the fix I need and I have contacted Support. They didn't seem to know what I was talking about and referred me to IT. They could not help me either. What does QFE stand for?

It is the fix I need and I have contacted Support. They didn't seem to know what I was talking about and referred me to IT. They could not help me either. What does QFE stand for?

QFE stands for Quick Fix Engineering and it is the Microsoft term for hot fixes. The fix is available for download upon request. Could you please escalate your ticket (if possible) so that it gets handled by someone familiar with this area? This posting is provided "AS IS" with no warranties, and confers no rights.

QFE stands for Quick Fix Engineering and it is the Microsoft term for hot fixes. The fix is available for download upon request. Could you please escalate your ticket (if possible) so that it gets handled by someone familiar with this area? This posting is provided "AS IS" with no warranties, and confers no rights.

QFE stands for Quick Fix Engineering and it is the Microsoft term for hot fixes. The fix is available for download upon request. Could you please escalate your ticket (if possible) so that it gets handled by someone familiar with this area? This posting is provided "AS IS" with no warranties, and confers no rights.

Hello,Thanks for your reply. I had a service request with the IT help desk, but I never had a ticket from Support. The first thing I need to know is who to call. Should I call support or the IT help desk? If I need to call support, would be able to give me the correct phone number? Also, once I havea ticket,I am not sure howto escalate my ticket.Thanks

Hello,Thanks for your reply. I had a service request with the IT help desk, but I never had a ticket from Support. The first thing I need to know is who to call. Should I call support or the IT help desk? If I need to call support, would be able to give me the correct phone number? Also, once I havea ticket,I am not sure howto escalate my ticket.Thanks

Hello,Thanks for your reply. I had a service request with the IT help desk, but I never had a ticket from Support. The first thing I need to know is who to call. Should I call support or the IT help desk? If I need to call support, would be able to give me the correct phone number? Also, once I havea ticket,I am not sure howto escalate my ticket.Thanks

Hello, I have problem with cascading parameters too. I my case, I have parameter User, and other: Customer . Those two parameters are multi-value. When I choose some value from User parameter, Customer parameter need to auto-select some relavite values. For example, when selected user are related with customer IBM, then this Customer (IBM) will be select on mulit-value list. It is important, to have opportunity to select other, not related with this User values from Customer parameter. I tried to fill Default Values based on DataSet. I create dataset selecting Customers related with customer and I define this dataset as Default Value with option "From query". When Customer parameter on start is empty, while selecting some User, Customer parameter has selected reated data. But when I change User, Cusotmer parameter has no action. The same Customers are selected, there are no change. How to do this ?

Hello, I have problem with cascading parameters too. I my case, I have parameter User, and other: Customer . Those two parameters are multi-value. When I choose some value from User parameter, Customer parameter need to auto-select some relavite values. For example, when selected user are related with customer IBM, then this Customer (IBM) will be select on mulit-value list. It is important, to have opportunity to select other, not related with this User values from Customer parameter. I tried to fill Default Values based on DataSet. I create dataset selecting Customers related with customer and I define this dataset as Default Value with option "From query". When Customer parameter on start is empty, while selecting some User, Customer parameter has selected reated data. But when I change User, Cusotmer parameter has no action. The same Customers are selected, there are no change. How to do this ?

Hello, I have problem with cascading parameters too. I my case, I have parameter User, and other: Customer . Those two parameters are multi-value. When I choose some value from User parameter, Customer parameter need to auto-select some relavite values. For example, when selected user are related with customer IBM, then this Customer (IBM) will be select on mulit-value list. It is important, to have opportunity to select other, not related with this User values from Customer parameter. I tried to fill Default Values based on DataSet. I create dataset selecting Customers related with customer and I define this dataset as Default Value with option "From query". When Customer parameter on start is empty, while selecting some User, Customer parameter has selected reated data. But when I change User, Cusotmer parameter has no action. The same Customers are selected, there are no change. How to do this ?

I have a problem with SSRS 2008 parameters as well.The same RDL report parameters that worked on ssrs 2005 -- failed to update correctly when moved to ssrs 2008. in my case, i have a parameter for "date range" called: (drop down) for Today, Yesterday, last Month, last quarter... and then two boxes that calculate those values:so last month would populate to more parameters: From: April 1To: April 30And then I can view the report which takes the from & to dates parametersThis worked in SSRS 2005 but now - it doesn't auto-update on ssrs 2008. And it works in Visual Basic Studio 2008 (BI Studio) too. it's just ssrs 2008 that doesn't seem to like the code or the parameters. again, same rdl...

Recently released CU#5 contains the fix for this issue.KB:http://support.microsoft.com/default.aspx/kb/969531/en-usIf it doesn't solve the issue you have with the report, please file a bug through Microsoft Connect.Thanks,Tau This posting is provided "AS IS" with no warranties, and confers no rights.

Do you know where I can get the CU#5 in 64bit? I didn't see that option on the link you provded above.

Sorry. I needed to use the browser from my server (64bit) and that fixed the issue. Now to add to that though: I got these two file download options: SQL_Server_2008_RTM_CU5_SNACSQL_Server_2008_Cumulative_Update_5What are the differences?

as a follow up, I installed: SQL_Server_2008_Cumulative_Update_5 (222MB) and this solved my issue with the parameters.

After a few attempts I finally got the hot fix and the problem is resolved!

Thanksfor confirming that CU#5 (http://support.microsoft.com/default.aspx/kb/969531/en-us) resolves the issue. In summary, CU#5 is available for x86, x64, and ia64 and you need to install the full CU#5 package (> 200 MB download).Thanks,RobertRobert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

I installed this on my dev server without problemI ran the install in production and my ssrs instance does not show up under the options. all i see is the "shared Features" check box... Can you help?

Hi Tau,I have installed Cumulative Update 2 from this link http://support.microsoft.com/kb/970315and still cascaded parameters are not working.Strange thing is, I have some reports, which I have converted from RS2005 to RS2008. In the converted reports cascaded parameters are working fine. It is just the reports, which I am creating in RS2008 from scratch.Any clue.Regards,Ashish

Hi Tau,I have installed Cumulative Update 2 from this link http://support.microsoft.com/kb/970315and still cascaded parameters are not working.Strange thing is, I have some reports, which I have converted from RS2005 to RS2008. In the converted reports cascaded parameters are working fine. It is just the reports, which I am creating in RS2008 from scratch.Any clue.Regards,Ashish

Hi Tau,I have installed Cumulative Update 2 from this link http://support.microsoft.com/kb/970315and still cascaded parameters are not working.Strange thing is, I have some reports, which I have converted from RS2005 to RS2008. In the converted reports cascaded parameters are working fine. It is just the reports, which I am creating in RS2008 from scratch.Any clue.Regards,Ashish

Ashish,RS 2008 RTM + CU#5 does have the cascading parameters fixed.RS 2008 RTM + SP1 with any other CU#5 does not have the cascading parameters fixed.Edgar.

Ashish,RS 2008 RTM + CU#5 does have the cascading parameters fixed.RS 2008 RTM + SP1 with any other CU#5 does not have the cascading parameters fixed.Edgar.

Ashish,RS 2008 RTM + CU#5 does have the cascading parameters fixed.RS 2008 RTM + SP1 with any other CU#5 does not have the cascading parameters fixed.Edgar.

Has the exact scenario that I posted been tested? I know that part of the cascading parameter issue was fixed, but not the whole thing. The problem I described above has been an issue since SSRS 2005.

Has the exact scenario that I posted been tested? I know that part of the cascading parameter issue was fixed, but not the whole thing. The problem I described above has been an issue since SSRS 2005.

Has the exact scenario that I posted been tested? I know that part of the cascading parameter issue was fixed, but not the whole thing. The problem I described above has been an issue since SSRS 2005.

Dear Robert, CU5 for SQL Server 2008 includes KB 969453 which resolves some issues with cascading parameters, but CU2 for SQL Server 2008 SP1 does not include it. CU5 cannot be installed on SP1. How can cascading parameters issues be fixed on SQL Server 2008 SP1 ? Thank you, Sergey

Dear Robert, CU5 for SQL Server 2008 includes KB 969453 which resolves some issues with cascading parameters, but CU2 for SQL Server 2008 SP1 does not include it. CU5 cannot be installed on SP1. How can cascading parameters issues be fixed on SQL Server 2008 SP1 ? Thank you, Sergey

Dear Robert, CU5 for SQL Server 2008 includes KB 969453 which resolves some issues with cascading parameters, but CU2 for SQL Server 2008 SP1 does not include it. CU5 cannot be installed on SP1. How can cascading parameters issues be fixed on SQL Server 2008 SP1 ? Thank you, Sergey

Hello Sergey,the cascading parameters fix will be included in SP1 CU#3, which will be available for downloadin about 5 weeks.HTH,RobertRobert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

Hello Sergey,the cascading parameters fix will be included in SP1 CU#3, which will be available for downloadin about 5 weeks.HTH,RobertRobert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

Hello Sergey,the cascading parameters fix will be included in SP1 CU#3, which will be available for downloadin about 5 weeks.HTH,RobertRobert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Ashish,As Edgar and Robert pointed out, SP1 CU#2 doesn't contain the cascading parameters fix, and itwill be included in SP1 CU#3, which will be available for downloadin another 5 weeks.Hope this helps,TauThis posting is provided "AS IS" with no warranties, and confers no rights.

Hi Ashish,As Edgar and Robert pointed out, SP1 CU#2 doesn't contain the cascading parameters fix, and itwill be included in SP1 CU#3, which will be available for downloadin another 5 weeks.Hope this helps,TauThis posting is provided "AS IS" with no warranties, and confers no rights.

Hi Ashish,As Edgar and Robert pointed out, SP1 CU#2 doesn't contain the cascading parameters fix, and itwill be included in SP1 CU#3, which will be available for downloadin another 5 weeks.Hope this helps,TauThis posting is provided "AS IS" with no warranties, and confers no rights.

Is there a solution for this for Reporting Services 2005?

Is there a solution for this for Reporting Services 2005?

Is there a solution for this for Reporting Services 2005?

What is discussed in this thread is about a difference between RS 2005 and RS 2008 RTM behavior. The fixavailable in RS 2008RTM CU#5, and SP1 CU#3 is to make RS 2008 behave the same as RS 2005.I'm curious,what is the specific problem in RS 2005 you are looking for a solution?Robert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

What is discussed in this thread is about a difference between RS 2005 and RS 2008 RTM behavior. The fixavailable in RS 2008RTM CU#5, and SP1 CU#3 is to make RS 2008 behave the same as RS 2005.I'm curious,what is the specific problem in RS 2005 you are looking for a solution?Robert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

What is discussed in this thread is about a difference between RS 2005 and RS 2008 RTM behavior. The fixavailable in RS 2008RTM CU#5, and SP1 CU#3 is to make RS 2008 behave the same as RS 2005.I'm curious,what is the specific problem in RS 2005 you are looking for a solution?Robert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Robert, It's the cascading parameters fix. The first parameter choice is supposed to update the 2nd parameter drop down list that is multi-value enabled, but doesn't seem to refresh after making another choice in the first parameter. It's the same problem as this post: http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/6d86de1f-6b30-4368-bc07-47255ff907f3/ Thanks.

Hi Robert, It's the cascading parameters fix. The first parameter choice is supposed to update the 2nd parameter drop down list that is multi-value enabled, but doesn't seem to refresh after making another choice in the first parameter. It's the same problem as this post: http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/6d86de1f-6b30-4368-bc07-47255ff907f3/ Thanks.

Hi Robert, It's the cascading parameters fix. The first parameter choice is supposed to update the 2nd parameter drop down list that is multi-value enabled, but doesn't seem to refresh after making another choice in the first parameter. It's the same problem as this post: http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/6d86de1f-6b30-4368-bc07-47255ff907f3/ Thanks.

The problem is with SSRS 2008 AND 2005. If you do the following with any report, you will see the behavior I'm referring to:1. Choose SELECT ALL for the 1st inter-dependent parameter. This will work as expected.2. Go back to the 1st parameter, unselect SELECT ALL, and choose a 1 value. This will work as expected.3. Go back to the 1st parameter, chooseSELECT ALL. The dependent parameters will not be udpated as expected.

The problem is with SSRS 2008 AND 2005. If you do the following with any report, you will see the behavior I'm referring to:1. Choose SELECT ALL for the 1st inter-dependent parameter. This will work as expected.2. Go back to the 1st parameter, unselect SELECT ALL, and choose a 1 value. This will work as expected.3. Go back to the 1st parameter, chooseSELECT ALL. The dependent parameters will not be udpated as expected.

The problem is with SSRS 2008 AND 2005. If you do the following with any report, you will see the behavior I'm referring to:1. Choose SELECT ALL for the 1st inter-dependent parameter. This will work as expected.2. Go back to the 1st parameter, unselect SELECT ALL, and choose a 1 value. This will work as expected.3. Go back to the 1st parameter, chooseSELECT ALL. The dependent parameters will not be udpated as expected.

L.M.: Ahhh rats. It's both versions then. Yes that's the same thing, basically the 2nd parameter isn't refreshing properly. It's a pity this has been dragging on for 2-3 years (based on forum posts I've seen). Okay workarounds, is there a way to check my selection from Parameter 1 so that Parameter 2 becomes activated (enabled) or deactived? I only need Parameter 2 to be active based on only one choice in Parameter 1. The other choices in Parameter 1 don't need Parameter 2 to be active. Thanks.

L.M.: Ahhh rats. It's both versions then. Yes that's the same thing, basically the 2nd parameter isn't refreshing properly. It's a pity this has been dragging on for 2-3 years (based on forum posts I've seen). Okay workarounds, is there a way to check my selection from Parameter 1 so that Parameter 2 becomes activated (enabled) or deactived? I only need Parameter 2 to be active based on only one choice in Parameter 1. The other choices in Parameter 1 don't need Parameter 2 to be active. Thanks.

L.M.: Ahhh rats. It's both versions then. Yes that's the same thing, basically the 2nd parameter isn't refreshing properly. It's a pity this has been dragging on for 2-3 years (based on forum posts I've seen). Okay workarounds, is there a way to check my selection from Parameter 1 so that Parameter 2 becomes activated (enabled) or deactived? I only need Parameter 2 to be active based on only one choice in Parameter 1. The other choices in Parameter 1 don't need Parameter 2 to be active. Thanks.

Maybe you can use an expression in the parameter value of the dataset? Off hand, I'm not really sure. We've just been living with it, unfortunately.

Maybe you can use an expression in the parameter value of the dataset? Off hand, I'm not really sure. We've just been living with it, unfortunately.

Btw, SP1 CU#3is available now for download: http://support.microsoft.com/kb/971491Robert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

Btw, SP1 CU#3is available now for download: http://support.microsoft.com/kb/971491Robert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

Btw, SP1 CU#3is available now for download: http://support.microsoft.com/kb/971491Robert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

from my testing, CU3 didn't fix the cascading parameter.

from my testing, CU3 didn't fix the cascading parameter.

Could you please be more specific on what is now working? Also, could you please check the file version of Microsoft.ReportingServices.ProcessingCore.dll in server bin directory? It is supposed to have a file version 10.0.2723.0 ((Katmai_SP1_QFE-CU).090710-0129 after the patch is successfully applied. If the file version doesn't look correct, please follow the steps in the MSDN document below to apply the patch.http://msdn.microsoft.com/en-us/library/dd638066.aspxHTHTau This posting is provided "AS IS" with no warranties, and confers no rights.

Could you please be more specific on what is now working? Also, could you please check the file version of Microsoft.ReportingServices.ProcessingCore.dll in server bin directory? It is supposed to have a file version 10.0.2723.0 ((Katmai_SP1_QFE-CU).090710-0129 after the patch is successfully applied. If the file version doesn't look correct, please follow the steps in the MSDN document below to apply the patch.http://msdn.microsoft.com/en-us/library/dd638066.aspxHTHTau This posting is provided "AS IS" with no warranties, and confers no rights.

Could you please be more specific on what is now working? Also, could you please check the file version of Microsoft.ReportingServices.ProcessingCore.dll in server bin directory? It is supposed to have a file version 10.0.2723.0 ((Katmai_SP1_QFE-CU).090710-0129 after the patch is successfully applied. If the file version doesn't look correct, please follow the steps in the MSDN document below to apply the patch.http://msdn.microsoft.com/en-us/library/dd638066.aspxHTHTau This posting is provided "AS IS" with no warranties, and confers no rights.

bumpingKarthick

Btw, SP1 CU#3 is available now for download: http://support.microsoft.com/kb/971491 Robert Bruckner http://blogs.msdn.com/robertbrucknerThis posting is provided "AS IS" with no warranties, and confers no rights. Robert,I'm curious as to what specific KB article number in this CU addresses the issues proposed in this thread.Thanks,jb

Btw, SP1 CU#3 is available now for download: http://support.microsoft.com/kb/971491 Robert Bruckner http://blogs.msdn.com/robertbrucknerThis posting is provided "AS IS" with no warranties, and confers no rights. Robert,I'm curious as to what specific KB article number in this CU addresses the issues proposed in this thread.Thanks,jb

Btw, SP1 CU#3 is available now for download: http://support.microsoft.com/kb/971491 Robert Bruckner http://blogs.msdn.com/robertbrucknerThis posting is provided "AS IS" with no warranties, and confers no rights. Robert,I'm curious as to what specific KB article number in this CU addresses the issues proposed in this thread.Thanks,jb

The specific change is only called out in the RTM CU#5 KB article http://support.microsoft.com/kb/969531 (the same fix was ported and available starting with SP1 CU#3): 288137 KB 969453 (http://support.microsoft.com/kb/969453/ ) FIX: The cascading report parameters are inconsistent in a SQL Server 2008 Reporting Services report that contains three or more levels of cascading report parameters Unfortunately the detailed KB 969453 does no longer seem to be available.HTH,RobertRobert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

The specific change is only called out in the RTM CU#5 KB article http://support.microsoft.com/kb/969531 (the same fix was ported and available starting with SP1 CU#3): 288137 KB 969453 (http://support.microsoft.com/kb/969453/ ) FIX: The cascading report parameters are inconsistent in a SQL Server 2008 Reporting Services report that contains three or more levels of cascading report parameters Unfortunately the detailed KB 969453 does no longer seem to be available.HTH,RobertRobert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

The specific change is only called out in the RTM CU#5 KB article http://support.microsoft.com/kb/969531 (the same fix was ported and available starting with SP1 CU#3): 288137 KB 969453 (http://support.microsoft.com/kb/969453/ ) FIX: The cascading report parameters are inconsistent in a SQL Server 2008 Reporting Services report that contains three or more levels of cascading report parameters Unfortunately the detailed KB 969453 does no longer seem to be available.HTH,RobertRobert Bruckner http://blogs.msdn.com/robertbruckner This posting is provided "AS IS" with no warranties, and confers no rights.

Edgar, In your note from May 29,2009 you said that you installed SQL_Server_2008_Cumulative_Update_5 (222MB) . Where did you get 222MB file, the ZIP file is 176MB and I unzip the files still almost the same size 176MB. Please let us know where did you get the 222MB file Thanks Jose

Edgar, In your note from May 29,2009 you said that you installed SQL_Server_2008_Cumulative_Update_5 (222MB) . Where did you get 222MB file, the ZIP file is 176MB and I unzip the files still almost the same size 176MB. Please let us know where did you get the 222MB file Thanks Jose

Edgar, In your note from May 29,2009 you said that you installed SQL_Server_2008_Cumulative_Update_5 (222MB) . Where did you get 222MB file, the ZIP file is 176MB and I unzip the files still almost the same size 176MB. Please let us know where did you get the 222MB file Thanks Jose

I don't remember specifically but it was in the download page. Login to via your server and the MS site will determine if you need the 64bit or 32bit... size might vary. I had 64bit OS