Sorry Mark, I'm not understanding why this would be a two page "thing". The way I would envision this is as follows:
1) Navigate to reports.aspx
2) Choose and rpt
3) Select parameters
4) Build dataset based on the selected parameters in (3)
5) Load report selected in (2)
6) Point the report at the dataset created in (4)
The above would be my preferred way. Now, I suspect the issue is in the implementation details of (3). In the above flow, you would not use the CR parameter input form. You'd have to create your own parameter input. If you are trying to use the CR viewer parameter form, then yes, you'd need a larger dataset that will hopefully have the data specified by the parameter. But then the whole workflow would change to:
1) Navigate to reports.aspx
2) Choose and load rpt
3) Point rpt at dataset
4) Refresh report - forcing a parameter prompt
5) Send report to viewer / export / print
I still do not see a two page thing happening here(?), or is the parameter prompt what you'd call the second page?
- Ludek