Example Testing Scenarios—When Caption and Key Bindings Differ

When testing a drill-through report, the value you enter in the Column Value field of the Drill-through Report Testing dialog must be a value that represents the key binding expression of the dimension element in the intersection.

In general, the value of the key binding expression of a dimension element is the same as the value of the caption binding expression, which represents an outline member name. However, some hierarchies that are used to create drill-through report intersections may have been built using dimension elements where the caption binding differs from the key binding. This is the case when the Advanced or Delayed options are selected for the key binding of a dimension element.

The following example procedures contain scenarios for testing drill-through reports when intersections contain elements that use the Advanced and Delayed options. See these topics:

Note:

The example procedures assume you have created a data source connection to the sample TBC database.

Advanced Option Example

To test with a hierarchy that uses the Advanced option in a dimension element:

Create a dimension element called SKU_Advanced, basing the caption binding expression on SKU from the TBC database, Product table (TBC.PRODUCT); for example:
```
connection : \'tbcSource'::'TBC.PRODUCT'.'SKU’
```
Set the Key Binding type to Advanced.
Base the Key Binding expression on the PRODUCTID column from the Product table (TBC.PRODUCT); for example:
```
connection : \'tbcSource'::'tbc.product'.'PRODUCTID'
```
Create a “product_advanced” hierarchy with the FAMILY column from the FAMILY table as the parent level, and the SKU_Advanced dimension element as the child.
Create a cube schema and Essbase model using the product_advanced hierarchy you created in step 4; use AMOUNT from TBC.SALES as the measure.
Create a drill-through report (File, then New, and then Drill-through Report) as specified below:
1. In the Context tab, add the product_advanced hierarchy.
2. In the Report Contents tab, place any fields from TBC.PRODUCT, for example: CAFFEINATED or PKGTYPE.
Click Test to launch the Drill-through Report Testing dialog box.
Click the drop-down arrow in the first row under Intersection and select SKU_Advanced.
In Column Value, enter a value that represents the value shown in the key binding expression in step 3.
Using the hierarchy created in this scenario, enter a value from the PRODUCTID column; for example:
```
1
```
Click Show Result.

Delayed Option Example

To test with a hierarchy that uses the Delayed option in a dimension element:

Create a dimension element called SKU_Delayed, basing the caption binding expression on SKU from the TBC database, Product table (TBC.PRODUCT); for example:
```
connection : \'tbcSource'::'TBC.PRODUCT'.'SKU’ 
```
Set the Key Binding type to Delayed.
Create a “product_delayed” hierarchy with the FAMILY column from the FAMILY table as the parent level, and the SKU_Delayed dimension element as the child.
In the hierarchy, the key binding expression for the SKU_Delayed element should display as:
```
class : \'tbcSource'\'family'\'FAMILY'.'caption' || "_" || class : \'DimElements'\'SKU_Delayed'.'caption'
```
Create a cube schema and Essbase model using the “product_delayed” hierarchy you created in step 3; use AMOUNT from 'TBC.SALES' as the measure.
Create a drill-through report as specified below:
1. In the Context tab, add the product_delayed hierarchy you created in step 3.
2. In the Report Contents tab, place any fields from TBC.PRODUCT, for example: CAFFEINATED or PKGTYPE.
Click Test to launch the Drill-through Report Testing dialog box.
Click the drop-down arrow in the first row under Intersection and select SKU_Delayed.
In Column Value, enter values that represent the values that are shown in the key binding expression in step 3.
Using the hierarchy created in this scenario, enter a value from the FAMILY column and a value from the SKU column, separated by an underscore. For example:
```
100_100-10 
```
Click Show Result.