In this case, jumping to another
report is the desired behavior, and dropping down the list shows the reports available
in this particular project.
Once the report has been selected, the developer can click on the Parameters
button to open the Parameters dialog box. This dialog box lists the parameters
on the report and allows the developer to choose what from the current report
should be passed to the parameters on the linked report. The first parameter is
the ProductCategory, and this should be set to whatever the user chooses as the
parameter on the current report. Unfortunately, simply dropping down the list
doesn??™t reveal the parameters from the current report, only the fields in the dataset.
Clicking on the Expression option opens the Edit Expression dialog box and
this does contain all of the parameters as well as the fields in the dataset, so the
parameter can be selected here. However, a couple of changes are needed.
First, the parameters have both a value and a label. The value is usually the
unique identifier in a cube, so it contains the dimension, hierarchy, and usually an
index number for the item. The SQL statement in the linked report won??™t understand
a product category of [Product].[Category].&[4] so the parameter will have to
be changed to use the label instead, which is the text the person sees in the list.
However, this introduces another problem; the values may be indented if they are at
a lower level of detail. Therefore, the developer will have to wrap the LTrim function
around the parameter, which removes all leading spaces from the value.
Pages:
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433