Showing posts with label selected. Show all posts
Showing posts with label selected. Show all posts

Monday, March 26, 2012

Problems displaying default value of first cascading parameters.

I have 5 cascading parameters. They all have default values. I would like the default value of each of these to be selected when the report opens.

It currently works correctly when I preview the report, however when I deploy the report to the server it does not. In the deployed report, the default value of the first parameter is not selected. However, when I select a value for this one, on postback the rest of these parameters get set to their default value. They're all configured the same. I'm confused as to why the first one doesn't default to its default value while the others do.

Got any ideas?

Here's how I have it configured:

Allow null value CHECKED

Allow blank value CHECKED

The rest are unchecked.

Available values: From query

Default Values: Non-queried with a value supplied that exists in the dataset.

This issue got resolved when I deleted all of my reports from the server and then redeployed them. Funny how that works...sql

Problems displaying default value of first cascading parameters.

I have 5 cascading parameters. They all have default values. I would like the default value of each of these to be selected when the report opens.

It currently works correctly when I preview the report, however when I deploy the report to the server it does not. In the deployed report, the default value of the first parameter is not selected. However, when I select a value for this one, on postback the rest of these parameters get set to their default value. They're all configured the same. I'm confused as to why the first one doesn't default to its default value while the others do.

Got any ideas?

Here's how I have it configured:

Allow null value CHECKED

Allow blank value CHECKED

The rest are unchecked.

Available values: From query

Default Values: Non-queried with a value supplied that exists in the dataset.

This issue got resolved when I deleted all of my reports from the server and then redeployed them. Funny how that works...

Friday, March 9, 2012

Problem: Non Cascading Params causing report reload on each select

When running a report I am noticing the following behaviour:
As each parameter is selected, the report is doing some kind of postback or
refresh despite the fact that none of the parameters are linked
(cascading/dependent parameters).
Why is this occuring?
It is very annoying to the user as a report with 8 params is reloading 8
times even before they run the report.
Virtually all the params are query based with a default of query based.
config
RS2005 sp1I think this is by design, no way to change, unless write custom code which
is time consuming... may be MS will improve in the furture versions. :-)
Amarnath, MCTS
"adolf garlic" wrote:
> When running a report I am noticing the following behaviour:
> As each parameter is selected, the report is doing some kind of postback or
> refresh despite the fact that none of the parameters are linked
> (cascading/dependent parameters).
> Why is this occuring?
> It is very annoying to the user as a report with 8 params is reloading 8
> times even before they run the report.
> Virtually all the params are query based with a default of query based.
>
> config
> RS2005 sp1