Unexpected or Empty Results When Drilling Through
In other cases, if no data or the wrong data appears, the source item might not be mapped to the target correctly or the values in the data sources might not be conformed (the values do not match in both data sources).
If you have the necessary permissions, you can debug drill-through definitions by using the drill-through assistant from the Go To page (right-click the selection in the source report and select Go To). You can view the passed source values and the mapping to the target report parameters. You can use this tool for both authored and package drill-through definitions.
You might be able to correct the problem by modifying the parameter mapping in the drill-through definition. For example, when you drill from a cube to a relational data source, sometimes no data is returned or the wrong data is returned because the business key values in the two data sources do not match. You can change the drill-through definition to pass the caption of the IBM® Cognos PowerCube member instead of the business key, but you must also change the target report to filter on the corresponding string value and not the business key value.
However, it is best to ensure the data sources are conformed. In this example, the business keys in the cube should match the business keys in the relational source. Filtering on a key is more efficient than filtering on a larger string that may or may not be indexed in the database.
For more information on data source conformance, search for "conformed dimensions" and "business keys" in the IBM Cognos Transformer User Guide.
Procedure
Results
You might also want to see Data Does Not Appear in a Target Report or the Wrong Data Appears. For more information about drill-through access, see the Drill-Through Access chapter in the IBM Cognos Business Intelligence Administration and Security Guide.