Wednesday, March 7, 2012

Parameters Dependencies when using Parameters!Name.Label

Hello:

I just recently bumped into this problem and I think I know what's causing it. This is the setup:

Report Parameters: FromDate, ToDate, DivisionalOffice, Manager, SalesRep

dsCalendarEvents Parameters: FromDate.Value, ToDate.Value, DivisionalOffice.Value,

dsDivisions Parameters: N/A

dsManager Parameters: DivisionalOffice.Value

dsSalesRep: DivisionalOffice.Label

When I query the ReportServices WS and scan the parameter dependencies for SalesRep it says there are four dependencies: FromDate, ToDate, DivisionalOffice and Manager!!!

If I change "dsSalesRep" to use "DivisionalOffice.Value" the ReportingServices WS parameter dependency scan returns only one dependency for "SalesRep" parameter!!!( This is the correct behavior )

Has anybody seen this behavior and more importantly, is there a work around?

Regards,

How is the parameter label defined? Is it an expression, or does is it just bound to a dataset field?

Are you using SSRS2005 with SP2 installed on the server?

-- Robert

|||

The DivisionalOffice parameter gets its values from dsDivisions

dsDivision returns two fields:

codeid >>> =Parameters!DivisionalOffice.Value

codedescription >>> = Parameters!DivisionalOffice.Label

I am using SSRS2000 SP2....

Pushing real hard to get SQL Server 2005 :)

|||

This works as you would like to work with SSRS2005 SP2 only; it won't in SSRS 2000. Sorry.

-- Robert

No comments:

Post a Comment