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

“BadTableMapping-TooManyProperties” after importing rule

SA-33549

Summary



We ran an activity but it fails, “BadTableMapping-TooManyProperties”

Error Messages



“BadTableMapping-TooManyProperties”


Steps to Reproduce

  1. • Import to one of the Nodes.
  2. • Run an activity from the Node used to import and this updates and saves this new Property.
  3. • Logging into another node in the Cluster.
  4. • Running the Activity from this other node but it fails, “BadTableMapping-TooManyProperties”
  5. • Checking Out and Checking In the Property on this other node and the Activity then works.


Root Cause



This issue was determined to be a product enhancement request.
For now, PRPC nodes require a restart to pick up new columns.


Resolution



An enhancement request, FDBK-18289, has been created for consideration by Pega Product Management.

Published February 21, 2017 - 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