First off... this ISN'T the classic cascading parameters refresh issue that plagued 2008 (and apparently fixed with a CU)... it may appear similar but considering I'm running 2008 R2 I'm inclined to think I'm dealing with something different. Scenario is as follows; I have a report with the upper four parameters as cascading parameters (all are behaving as expected)... the fifth parameter is a 'switch' (e.g. true or false) to alter chart visibility and the sixth and seventh parameters are dates (start and finish). The two date parameters have default values dependent on the fifth parameter using a similar expression to the following; =IIF(Parameters!FifthParameter.Value="True", Today(), DateAdd("d", -365, Today()) The issue is that these date parameters simply will not refresh when the fifth parameter is changed from default... I have verified the code is correct by altering the fifth parameters default value and confirming the date parameters change accordingly - but they will only do so on the first load... Am I missing something obvious here? UPDATE: I forgot to add that I have set the parameters to 'Always Refresh' (made no difference). Have also just noticed that the date parameters will refresh when I change the first parameter? Windza

As far as my observation is concerned, I found this is the bahaviour when only the default value of a parameter is set based on another parameters value. The workaround I use is to set the parameter's available values expression also the same as the expression for default value. Once that is done, during runtime, the input field refreshes the values correctly. But the input changes to a dropdown and therefore for date input it may not be desirable because the rich date selection features given by date picker control is gone when it changes to a dropdown. As I mentioned, this is my observation and would be pleased to know for any alternatives that does refreshing of default values while retaining the control type as date picker. Please click "Mark as Answer" if this resolves your problem or "Vote as Helpful" if you find it helpful. BH

Hi Windza, The behavior that default value of a parameter cannot be refreshed depend on another parameter is by design, there is an old Connect issue refer to your question as following: Default does not get refreshed for cascading parameters: https://connect.microsoft.com/SQLServer/feedback/details/268032/default-does-not-get-refreshed-for-cascading-parameters#tabs Please see the following similar thread as a reference , Parameter change does not refresh default values of dependent parameters: http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/c24a881f-f22c-481a-91d3-d4b1082f2f78/ If you have any question, please feel free to ask. Thanks, Eileen