IBM Support

References to columns in data sets do not resolve in Cognos Analytics 11.1.7

Troubleshooting


Problem

Upgrading to Cognos Analytics (CA) 11.1.7 and refreshing data sets might cause identifier references to not resolve in data modules, reports, and dashboards.
 

This information does not apply to:

  • Uploaded files
  • Data sets created while using Compatible Query Mode
  • Imported deployments with data from data sets, which have not been refreshed
  • Refreshed data sets where names assigned to identifiers and are identical

When a data set is refreshed or created, it includes internal schemata describing the columns it contains. The column names generated by CA 11.1.7 are not consistent with those used in previous releases. This can result in identifiers not being resolved by content (data modules and dashboards) referencing data sets which have been refreshed or re-created using CA 11.1.7.

In the following example, a data module is created in CA 11.1.6 referencing table metadata imported from a database. Each column in the data module is assigned a default value for the label and identifier properties. As shown in the following diagram, the default label and identifier names are derived from the table column name.  The value of the label is Customer Sid and the identifier is CUSTOMER_SID.


Data module table definition

When a data set is created using the metadata from the data module, it will include an internal schema describing the columns. The column names in the internal schema are derived from the label property.
 

Dataset pre CA 117

When this data set is referenced by a data module or dashboard, they will include references to the identifier. If the data set is refreshed using CA 11.1.7, new schema information is generated. Instead of using the label (Customer Sid) for the column name, the value assigned to the identifier (CUSTOMER_SID) is used. Subsequently, any data modules, dashboards, or reports will display errors such as shown because the column name references (Customer_Sid) cannot be found in the data set schema (CUSTOMER_SID).

Dashboard error in CA 1117


Dashboard error using direct dataset reference

Data module error in CA 1117

Symptom

One or more data sets created before Cognos Analytics (CA) 11.1.7 are refreshed using CA 11.1.7.  When a module, dashboard or report is executed or edited, one or more errors will be displayed due to identifier references not resolving.

 

Cause

CA 11.1.7 data sets generate schema information where the column name is using the incorrect property. Content created before CA 11.1.7 used name references which cannot be resolved.

Diagnosing The Problem

Applications upgraded to CA 11.1.7, content (data modules and dashboards) reference data sets which are refreshed using CA 11.1.7.  Errors are displayed indicating the identifiers cannot be resolved. If the data sets were refreshed or re-created using CA 11.1.7, identifier names might not resolve.

New content (data modules and dashboards) created in CA 11.1.7 referencing new data sets created in CA 11.1.7 do not display errors.

When CA 11.1.7 is upgraded to CA 11.1.7 FP1 or above, content created in CA 11.1.7 experiences similar errors to those seen when upgrading to CA 11.1.7. Data modules and dashboards need to be readjusted to refer to the correct column names.

Resolving The Problem

Upgrading to CA 11.1.7 FP1 and refreshing the affected datasets will generate schemas with the correct column names. This is the recommended path to resolving this issue.

While remaining on CA 11.1.7, one of the following steps can be used to adjust a data module

  • Restoring the datasets from a pre-CA 11.1.7 deployment
  • Readding the dataset to a data module
  • Adjusting the values in the identifier properties in the data module
Deployments created prior to CA 11.1.7 that include data from datasets will be imported using the correct column names. If datasets are replaced using such a deployment, they should not be refreshed using CA 11.1.7 to avoid creating new schema information.

If a dataset has to be refreshed to include new business data, data modules referencing it must be adjusted to use the new column names. In the user interface for data modules, open the data source panel, locate the affected dataset, delete, and reinsert it into the data module. The module now references the column names used by CA 11.1.7.

If datasets have a few columns, editing the values of the column identifier properties is another alternative approach.

Ensure the data module validation does not indicate any remaining errors pertaining to identifiers that it cannot resolve.


Note: the relink action will not resolve the column reference.


Source panel in data modules user interface
A dashboard may have been created by directly referencing a data set versus via a data module which references the data set. Unlike a data module, one cannot delete and re-insert the data set in the dashboard editor and the Relink action will not resolve the issue. References to the data set columns can be reset by dragging the same column name from the metadata tree to the same field property. Calculations added to the metadata tree of a dashboard that referenced columns from the data set will also need to be changed to use the expected identifier name.

 

Document Location

Worldwide

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTSF6","label":"IBM Cognos Analytics"},"ARM Category":[{"code":"a8m500000008d6yAAA","label":"Upgrading or Migrating"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1.7"}]

Document Information

Modified date:
25 November 2020

UID

ibm16349499