I'm having an issue passing two parameters to another report which uses cascading parameters. The values are being passed correctly, as I can see in the URL, but if the combination of the two (level 1 param and level 2 param) are not valid, then the level 2 param gets reset to the default based on the level 1 param. For example, I have a report that shows contract numbers and the contract status (active or inactive). I click the contract to drill down to the detail by customer and pass the contract's status (level 1) and contract ID (level 2). If I pass status:Inactive ID:25 but ID:25 isn't in the currently inactive list, then the contract ID is ignored and is defaulted back to contract ID 1 which is the first inactive contract.
Is there a way to prevent the cascading auto population of the second level parameter when drilling through?
I found a workaround for this (what I would consider to be a bug): create a boolean param called Is_DrillThrough on the subreport defaulting to false. I also create a secondary contract ID parameter. If a report drills through then it passes true to Is_DrillThrough and passes the contract ID to both params. Then in the initialize code fo the subreport, it checks if the Is_DrillThrough is true and resets the original cascaded contract ID parameter using the secondary parameter. This is an ugly workaround requiring changes to all reports involved, but it does the trick for now.