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

Unable to insert data in the database after schema changes

SA-48506

Summary



Unable to insert data in the database after schema changes. The user configuration has an external table with column,YOUR_COLUMN_NAME, and an exposed property, your_column_NAME.


Error Messages



com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties your_data_class your_schema.your_table PegaDATA your_column_NAME


Steps to Reproduce



Unknown.


Root Cause



A defect in Pegasystems’ code or rules. Two properties in the class hierarchy have the same name. As a result, during data retrieval from the database to determine the mapping for the table, an incorrect property is chosen and the mapping fails.


Resolution

Perform the following local-change:

On the External Mapping tab for the class, explicitly map the column to the property. In this case map column YOUR_COLUMN_NAME to property your_column_NAME

.

Published March 8, 2018 - 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