Hidden Parameters and Default Values

I am using RS SP1, and to use a hidden parameter that is NOT read
only, after uploading the report into report manager.. at this stage
the report works FINE, with all the other parameters (not hidden)
working, they are combinations of query based lookups with query based
defaults, and ones with defaults by an expression in the report.
However after i go into the properties of the report in report
manager, to the parameters tab, and set the check box of my hidden
parameter ON, and set the prompt to an empty string (so its a hidden
but not readonly parameter).. then save that
THEN
my other parameters whose DEFAULT values were written by an expression
in the report - NO LONGER WORK
arrgh,
anybody got a solution?
the only work around i can think of is have a DUMMY SQL call that
basically just selects the value of my expression. (since the
parameters whose default values are based on a query rather than
expression still work)
Karli'm sure this is a bug..
whenever i have a default value for a parameter (that isn't pulldown)
that is calculated with an expression , weather it is based on a query,
or just a pure expression, all works fine, until you go to report
manager, and change anything in the parameters (i'm changing an
unrelated parmeter to be hidden (readable but not visible), when you
apply, all the default value calculations cease to work :(
Karl Prosser wrote:
> I am using RS SP1, and to use a hidden parameter that is NOT read
> only, after uploading the report into report manager.. at this stage
> the report works FINE, with all the other parameters (not hidden)
> working, they are combinations of query based lookups with query
based
> defaults, and ones with defaults by an expression in the report.
> However after i go into the properties of the report in report
> manager, to the parameters tab, and set the check box of my hidden
> parameter ON, and set the prompt to an empty string (so its a hidden
> but not readonly parameter).. then save that
> THEN
> my other parameters whose DEFAULT values were written by an
expression
> in the report - NO LONGER WORK
> arrgh,
> anybody got a solution?
> the only work around i can think of is have a DUMMY SQL call that
> basically just selects the value of my expression. (since the
> parameters whose default values are based on a query rather than
> expression still work)
> Karlsql