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
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
06 May 2025
UID
ibm16349499