Parameter Valid Values

plengski


I am deploying an rdl that is being deployed in a server.But i am encountering a problem regarding the valid values of the parameter.My parameters have dependencies,and one of my parameter comes out with two dependencies.

Scenario :
User needs to input his userID to access Book A.
Book B needs Book A because the output will be depending on the its content.
And Book C depend on Book B.

Problem:
when deploying, only Book A will have the initial value.The dependency in Book B is only one,which is fine.It shows its valid values. But how about for Book C which have 2 dependencies Because it doesnt show it's valid values..

David Leibowitz

I am assuming your parameters are named:

Book A

Book B

Book C

Book C will display its valid valid values, after A and B have been selected. On initial display (unless you have defaults) it will appear as though there are none, but after selection of B, C will refresh. C really only has 1 dependency (B), not 2.

plengski

Thanks for the reply..But im just curious why my default values become null to the fact that i already have a default value..

John Vulner - MSFT

I may have misunderstood your question, but it sounds like you are asking why "Book C" is disabled and does not show any values until both "Book A" and "Book B" have been populated.

From your description, C depends on B which depends on A. In this case, RS cannot generate the lists of valid values or default values for C without having values for B because those expressions/queries reference B. After entering a value for B, you should see the default values for C provided they are also in C's valid values list.