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

Database-BadTableMapping-TooManyProperties issue



On creation of a new table and attempting to save, exceptions are marked in the pegaRULES logfile: Database-BadTableMapping-TooManyProperties

The issue is not reproduced in earlier environments.

Error Messages

Error message in the logs -
obj-save failed. Database-BadTableMapping-TooManyProperties

Steps to Reproduce

  1. Create a new table in Dev environment.
  2. Create the same table in User Acceptance Testing (UAT).
  3. Import related Dev rules to UAT.

Root Cause

User did not specify the properties in external mapping wizard of the class to the database.


Note the following items:
  • All the properties and column name from database should match with upper and lower case characters.
  • All the properties should be defined in external mapping tab of class wizard.


Published August 17, 2016 - Updated October 8, 2020

Was this useful?

50% 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