Biml and SSIS Frameworks - SQL Server Integration Services Design Patterns - page 574

=Iif(Fields!Status.Value="Failed", "Errors", Nothing)
Click the Add button and map the AppInstanceID parameter name to the [Ap-
pInstanceID] parameter value. Click the Add button again and map the PkgIn-
stanceID parameter name to the [PkgInstanceID] parameter value. Click the
f(x) button in the Omit column of each parameter mapping and add the following ex-
pression to each Set Expression for: Omit textbox:
=Iif(Fields!Status.Value="Failed", False, True)
As with the Application Instance report, the two previous property settings config-
ure the Action property of the Status value. If the status is "Failed" , clicking the
word Failed, which will appear to be a hyperlink, will cause the Errors report to dis-
play. When it displays, it will only show those error rows associated with the applica-
tion instance displayed in that row of data.
Let's test it! When we run the Package Instance report, it now appears as shown in
Figure A-32 .
Figure A-32 . “Failed hyperlinks” for the Package Instance report
Clicking a Failed link takes us to the Errors report for that package instance. Cool.
Now let's add the Events column to the Package Instance report. Add a column with
the header and data field hard-coded Events. Open the Text Box Properties window for
the Events data field and navigate to the Font page. Set the Color property to Blue and
the Effects property to Underline. Navigate to the Action page and set the Enable as an
Action property to Go to Report. Select the Events report from the Specify a Report
drop-down and click the Add button twice to map two parameters. Map the AppIn-
stanceID parameter name to the [AppInstanceID] parameter value and the
PkgInstanceID parameter name to the [PkgInstanceID] parameter value.
Close the Text Box Properties window and click the Preview tab to test. The Package
Instance report should appear as shown in Figure A-33 .