Hide/unHide

dear All,

I want to make a Report with attractive selection parameters.
That I mean, there is a parameter, Tparam (Time Param) which will activate other parameters (3 parameters: TimeA_1, TimeA_2 & TimeA_3. These selection values have been registered in the "Aviable values => non-queried".)

when Tparam selected TimeA_1 then Parameter for TimeA_1 will activated (and the others will be disappeared/hidden), vice versa for the other control (TimeA_2 & TimeA_3)

any idea to do that?

thank you...What you want is available, they are called Cascading Parameters, there is a tutorial here
http://msdn2.microsoft.com/en-us/library/aa337426.aspx|||

Hi SNMSDN,

In the link ,you sent i can't find any source regarding hiding or ignoring one parameter using another parameter.

Even i have another problem in setting null values . I have 5 cascading parameters ,level1,level2,level3,level4 and level5

when level1 is compulsory ,i had the remaining 4 parameters to accept for null and are made optional

for this i tried with "Allow null value option" in Report parameters but its not accepting

as an alternative i tried with default value 'Query based' to return null.

None of them directs me towards accepting null

It is aksing to select the parameter

It will be really a great help if some body faced some problem like this and resolved it

Thanks in advance

Raj Deep.A

|||

I have the same problem.

Basically, it appears that if you reference a parameter directly or indirectly via any other parameter's DS, then it will not respect the "Allow Null" setting for that parameter, since it thinks that it is implicitly required.

For example, I have a report with State & County parameters that both need to be set to enable "Allow Null". The County parameter references the State parameter's value within its Dataset, but no other parameter references the County parameter.

As a result, the County parameter respects the "Allow Null" setting, but the "State" parameter does not.

There MUST be a way around this restriction!!!

I have tried to hack around it by creating a dummy parameter called "StateFilter" that uses an expression to either return the Parameter!State.Value or Null, and then the County dataset references this parameter instead of the actual "State" parameter. However, this doesnt work either. Sql RS is "smart" enough to see the indirect reference and continues to treat State as a required parameter.

Help!!!

~Lance

|||

Nevermind.

I had forgotten about this wrinkle in how report parameters worked, but just now realized that you have to provide an option that has a value of NULL in order to select the "Allow Null" option. Makes sense when you think of it, but it would be nice if RS injected the NULL value option in such cases.

See this posting for the details:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1067464&SiteID=17