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 observed in log files




Unable to add user from PRPC in Production environment as the activity fails at Obj-Save method due to BadTableMappingException.
Developer has added few required user profiles manually in database using DML. 


Error Messages


2014-11-01 09:14:21,102 [ch Thread t=009c0b70] [TABTHREAD0] [DemoFW:01.01.01] (xxx_FW_DEMOFW_Data_TUSER.Action) ERROR| user1 - obj-save failed. Database-BadTableMapping-TooManyProperties xxx-FW-CMSFW-Data-TUSER KBGPGRPP.TUSER PegaDATA RT_USER_FULL_NM

From: (H3F1F2E175DC5E1A35028D1ACD50E7F52:









at com.pegarules.generated.activity.ra_action_adduser_af18bb15421566a9984956330dc3ea7b.step9_circum0(

at com.pegarules.generated.activity.ra_action_adduser_af18bb15421566a9984956330dc3ea7b.perform(



Steps to Reproduce


Create properties, RT_USER and map it to a column of same name in a fully exposed table. Introduce one more property .RT_USER_FULL_NM and create respective column in table and map them. 


Root Cause


Reported behavior was not manifesting in another environment (Model). On comparing the database class report from Modal with one from Production, it was found that developer had two properties namely, RT_USER and RT_USER_FULL_NM in the modal. And, RT_USER and .RT_USER_FULL_NM in the production. This dot prefix with the property name was causing this issue. 




Refer below link in Pega 7 Help and read Column Inclusion.



"If this Single Value property is to belong to a top-level object (not to an embedded page) in any concrete class, indicate whether this property is to appear in the Database Class Mappings gadget and Modify Schema wizard as a candidate for an exposed column:

Leave blank if you do not anticipate any benefit in making this property an exposed column. Choose Required or Recommended to record your intent that a database administrator extend a database table schema to expose this property. These choices cause this property to appear as a candidate for column exposure in the Database Class Mappings gadget and Modify Database Schema wizard."


Local change is to set Column Inclusion as required for property .RT_USER_FULL_NM in production environment.

Published January 31, 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