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

PRPC expecting columns for each property in external mapping



Pega shows an error when a class is mapped to a table that does not contain columns for each of the properties.

Error Messages Database-BadTableMapping-TooManyProperties

Steps to Reproduce

1. Create a class with external mapping to a table with fewer columns than there are properties.
2. Save the Object.

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment.  Each property in a class needs to map to one and only one column.  Additionally, the property names need to match the column names, and are case sensitive.


This issue is resolved by making the following change to the operating environment:

Add columns to the external table for each property (or removing properties without matching columns) and ensuring that all names match.

Published June 12, 2015 - 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