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

Cannot migrate custom data table



When creating a class Data-Corr-BlockEmail using the data table wizard, even when the "create dedicated database table" is not selected.

It creates a table called HISTORY-DATA-CORR-BLOCKEDEMAIL.

Error Messages

" The bundle requires changes to the database schema. You do not have permissions to perform schema migration. Please download the SQL DDL, execute it and continue the wizard."

Steps to Reproduce


Root Cause

User assumed that the "create dedicated database table" meant no table would be created which is incorrect.


The issue you reported is not a bug but actually as per design, it still follows the same pattern even in Pega 7.x versions.

The table being created is the history table for the class being created that is, data-corr-blockemail and this is automatic for Data- classes and not related to the "create dedicated database table" option. This option if selected will create a dedicated table for the concrete class and would have been named pr_data_corr_blockemail.

The way to stop a dedicated history class being created for these types of classes is how user solved issue is to change the database/AutoDBSchemaChanges to False, create class and then change the value back later.


Published July 27, 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