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

No code generated for expression errors



An activity failed with the error "No code generated for expression."

Error Messages

Error during load of declarative page Declare_TestData Class mismatch for page Declare_TestData: Expected Sample-Work, found @baseclass

Caused by: ** No code generated for expression
at com.pega.pegarules.priv.FUAUtil.throwUnresolvedAssemblyError(

Steps to Reproduce

1. Configure an activity with a Property-Set step that references data on a data page.
2. Run the activity.

Root Cause

The root cause of this problem was the "Class mismatch" error in the data page rule. This caused UnresolvedAssemblyError in the activity that referenced the data page.


Correct the "Class mismatch" error in the data page rule, and resave the referencing activity.

Published May 25, 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