Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Exposed Columns Not Recognized - Report Denition



Error occurs when running reports on a newly set up Azure cloud system with an MSSQL database which does not have User Defined Functions (UDF) installed. The reports are created on an existing Pega 7.3.1 system with an Oracle database and moved to a Product rule file. This generates the Data Definition Language (DDL) for the table definitions.

Error Messages

An error occurred on executing the query for the report definition - There was a problem getting a list: code: 4121 SQLState: S0001 Message: Cannot find either column "DATA" or the user-defined function or aggregate "DATA.pr_read_from_stream", or the name is ambiguous.

DatabaseException caused by prior exception: Cannot find either column "DATA" or the user-defined function or aggregate "DATA.pr_read_from_stream", or the name is ambiguous.

| SQL Code: 4121 | SQL State: S0001

Steps to Reproduce

  1. Build Pega 7.3.1 on an Oracle system and Pega 7.4 on Azure and MSSQL system.
  2. Create a Product rule from the implementation on Pega 7.3.1 and import the Product rule to the Pega 7.4 system.
  3. While performing this, download the DDL query and run it manually in the Pega 7.4 system.
  4. Create a report definition with exposed columns.
  5. Run the report definition.

Root Cause

An issue in the custom application code or rules.
The column and property names were different in terms of casing.


Perform the following local-change: 
  1. Identify the affected tables.
  2. On the source system, for each affected table:

    - Find all the Data-Admin-DB-Tables that refer to the same table.
    - Update each table to use the exact same table name casing.
    - Re-export the application from the source system.

  3. On the target system, drop the current tables (if the table is empty) or drop only the affected columns (if there are rows).
  4. Re-import the application on the target system.
  5. On the target system, run column population tools or re-save the instance to populate the correctly-cased columns for non-empty tables.

Published May 1, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us