Troubleshooting
Problem
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.
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.
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).
Symptom
Cause
Diagnosing The Problem
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
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.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
25 November 2020
UID
ibm16349499