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

Class not saved with Concrete type



On creating a class of type Concrete in the Organizational Data layer, error occurs on saving the class record.

Error Messages

Save Failed - Trying to save an Invalid page:Table doesn't exist in Database.

Trying to save an invalid page:page is not valid.

Steps to Reproduce

  1. Create a class of type Concrete in Organizational Data layer (that is, Org-Data).
  2. Save the class.

Root Cause

A defect or configuration issue in the operating environment.
After code migration, the pr_history_* table mapped to the History-Org-Data class in the Data-Admin-DB-Table record, was missing.


Here’s the explanation for the reported behavior:

The user had changed the Data-Admin-DB-Table of History-Org-Data class mapping to the out-of-the-box pr_history table.

Perform the following local-change:
  1. Identify the missing History tables.
  2. Import these tables from another environment.
  3. Change the Data-Admin-DB-Table of the History-Org-Data class mapping to pr_history_* table (that is, the original History table).

Published March 25, 2020 - 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