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
- • Import to one of the Nodes.
- • Run an activity from the Node used to import and this updates and saves this new Property.
- • Logging into another node in the Cluster.
- • Running the Activity from this other node but it fails, “BadTableMapping-TooManyProperties”
- • 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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.