strange refresh of the parameter area

strange refresh of the parameter area

• Dave Biggins

   

  Is there any way of "turning off" this postback

  My parameters are never associated/dependant, and I'd like to disable this feature as it slows down our users.

  TIA

  
  

• wbeard52

  Hi Brian,

  my RS create a parameter for the date call @dtStartDate this will store the 1st prev monday date from now.

  in this case will be 6 March, and all data will create basic on this parameter, so the result will take this week result for the report. But is it anyway to allow me to change the value in parameter to other date anytime to view the data for other period

  so let say after i upload the report to report manager, can i just change the date to 27 Feb 2006 then reload all other dependency parameter and the out put of the report

  regards

  terence chua

  
  
  

• Billo355

  It's possible that the expression used for the second parameter is too complex for report server to parse.  In this case, it falls back to assuming that there is a dependency.  Your only workaround in this case would be to reorder the parameters such that the more complex one is first.  Parameters can only be dependent on earlier parameters, so the report server would not see a dependency.

  
  

• nikhilkapur

  We have the same problems with our report parameters in several of our reports but we dont use expressions nor dependencies. All report parameters are mainly connected to 2 data sets. 1 for populating the dropdown and the other is for populating the default values.

  My question is, why are we still getting post backs on the report parameter regions. Post backs are ok if we have only a couple parameters. But most of our reports has an average of 8 report parameters. These postbacks gets quite annoying.

  
  
  

• Jimbo M

  Unfortunately, no.  Short of disabling the entire parameters area and using your own parameter prompts, there is no way to turn it off.  The only thing you can do is remove the perceived dependency by reordering the parameters or getting rid of the dynamic default/valid values query.
  

• Sebastien A

  Is there a checklist that we can look at when creating parameters to avoid having post backs
  
  

• mjwills

  The problem is having any code in the default expression, my assumption is you might be defaulting the date. Using VB, or even just =1 is enough for RS to have to reevaluate.

  There is a solve I found though...convert that to SQL and use a dataset instead. This does not seem to cause a strange refresh of parameters in reporting services.

  More info here:

  http://maxqtech.com/CS/blogs/david_leibowitz/archive/2007/02/08/3520.aspx

  
  
  

• Denis Repke

  Brian,
  
  I am experiencing exactly the same issue. The first parameter is a drop down, the second date , etc.
  
  As soon as change something in 1st parameter, Report Manager is trying to refresh but I have checked everything and there is NO dependency with the other parameters except that this is a paremeter to the store procedure that will be used to display day within the report
  
  This is very annoying to our user community !!
  
  I was actually hoping in SQL 2005 to have an option that could help avoid refreshing when I wanted
  
  Help
  
  Maria
  
  

• alexandrupaul

  Do you have a dependency between the first and second parameters   If so, clicking out of the first parameter will cause the viewer to auto-postback so that the valid values and default values for the second parameter are updated.  To verify that this is the case, instead of clicking on the second parameter, just click the background of the viewer.  That should cause the same refresh.
  

• Shalabh Gupta

  I also have this issue. I only have 2 parameters which are @StartDate and @EndDate. For some strange reasons, only the dropdown list for the @StartDate would cause a refresh. I don't want to reverse the order of the 2 since obviously this will confuse users. Is there a way to just simply turn off postbacks for the parameters Btw, I tried reversing the order, but the postback still happens to whichever is the first parameter in the order.
  
• strange refresh of the parameter area