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

Can't use property in this report.



Customer modified external database schema. After that, report on PRPC fails to pick up the schema change. Following message is written to Pega log. Can't use property "MU_1_TOUGETU" in this report. It's not a column and it doesn't exist in the Blob.
at com.pega.pegarules.priv.desktop.reporting.ContentBuilder.getListSelectClause(
at com.pegarules.generated.getListSelectClause_060301_CQK5de2CEtUnzrCPT01G4g.getListSelectClause06_03_01(
at com.pegarules.generated.getListSelectClause_060301_CQK5de2CEtUnzrCPT01G4g.invoke(
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(

Error Messages

Can't use property "MU_1_TOUGETU" in this report. It's not a column and it doesn't exist in the Blob.


The imported Jar file contains code which accesses the updated schema of external database. However, the schema in the external database was not yet updated when Jar file was imported.

Re-saving corresponding database table and testing the connection resolved the issue.

Published January 31, 2016 - Updated October 8, 2020

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