Support Article
Database-BadTableMapping-TooManyProperties issue
SA-26510
Summary
On creation of a new table and attempting to save, exceptions are marked in the pegaRULES logfile: com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties
The issue is not reproduced in earlier environments.
Error Messages
Error message in the logs -
obj-save failed.
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties
Steps to Reproduce
- Create a new table in Dev environment.
- Create the same table in User Acceptance Testing (UAT).
- Import related Dev rules to UAT.
Root Cause
User did not specify the properties in external mapping wizard of the class to the database.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.