Debugging a Drill-through Definition
It can also help you understand how the drill-through functionality works, especially across different types of data sources. This functionality is also referred to as the drill-through assistant. You can also debug drill-through definitions that were created in a PowerCube and migrated to IBM Cognos BI.
If your target report is not receiving any parameters, check the mapping in your drill-through definition, and ensure that your parameters were created against the correct data type for your drill-through scenario. For example, if you want to create a drill-through definition from an OLAP package to a target report based on a relational package, your target parameters need to be set up to a query item that has the same value as the OLAP business key or the member caption. For more information, see Members and Values.
If your target report is being filtered with the wrong values, check the values that are being mapped from the source to the target.
You must have the necessary permissions to use the drill-through assistant. The information that the drill-through assistant provides is available from the Go To page, when you run the drill-through. The drill-through assistant provides the following information.
Passed Source Values
The source values are the values from the selection context that are available for passing to the target report when the user chooses to drill through to the target report or object. For example, if you drill through from a source in Analysis Studio, you see the values at the intersection you selected before the drill-through action, and any values in the context area.
The values in the debug list are the values in the source report that were transformed by any drill-through operation.
- Display Value
Shows the value that users see when using this data item or this member. For OLAP members, this is the member caption or label. For example: Telephone is a member from the Order Method dimension.
- Use Value
Shows the value that IBM Cognos reports and analyses use when retrieving the data item or the member. For OLAP members, this is the member unique name (MUN). For example: [great_outdoors_company].[Order Method].[Order Method].[Order Method1]->:[PC].[@MEMBER].[2] is the MUN for the Telephone member in the Order Method dimension.
Target Mapping
If you chose to use parameters in the target, then the target mapping shows the name of each parameter that was mapped in the drill-through definition, and the values that the source is attempting to pass to that parameter.
- Parameter Name
Shows a list of valid target parameters mapped in the drill-through definition to receive information from the query item, level, or hierarchy on which you performed the drill-through action.
You can see only parameters for which there is a valid mapping and only the names of the parameters. For example, if the target report contains a parameter for Product Type and the drill-through definition maps that target parameter to the source Product Type level metadata, you see this target parameter only if you attempt to drill through on the Product Type level in the source report. Drilling through on the Product Line level does not display this parameter target.
You must ensure that the target parameters in your drill-through definitions are mapped correctly. Incorrectly mapped parameters can receive information from the wrong source metadata, especially where you have data values that are not unique. If you cannot see any target parameters or the parameters you expected to see in the View Target Mapping list, check the parameter mapping in the drill-through definition.
- Display Value
Shows the value that users see when using a data item or member. For OLAP members, this is the member caption or label. For example: Telephone is a member from the Order Method dimension
- Use Value
Shows the transformed value that the drill-through definition uses when passing a data item value or member to the target parameter.
OLAP members passed to relational target parameters obtain the business key from the members MUN and pass only the business key. Using the example of the Telephone member in Order Methods, the business key is 2. If you are unsure of what the business key is for a member, you can write a Report Studio expression such as roleValue('_businessKey',[member]). This value is passed to the target parameter.
OLAP members passed to a target parameter based on another OLAP package of the same OLAP type show a transformed MUN. Using the Order Methods example, the MUN is now transformed and the drill-through definition uses the value of [great_outdoors_company].[Order Method].[Order Method].[Order Method1]-> [Order Method1]. [2]:[PC].[@MEMBER].[2]. The middle portion of [Order Method1][2] is where the drill-through definition finds the correct member in the target when the OLAP data sources are different. To see the MUN for a specific member, you can look at the properties of the member in Report Studio and look at the Member Unique Name property.