PRException sometimes appears during product import
The Administrators have built a Product rule in order to transfer an existing application to a new PRPC instance, where the application contains two circumstanced rules based on different properties.
They have exported the product file without error.
But when attempting to import his into a second environment, after clicking on the Import button the only change seen by the operator is the Import button gets disabled and remains that way.
This is also accompanied by the error below in the log files.
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties Index-CircumstanceDefinition pr_index_circumstance_def PegaRULES IsEditWithoutSave
... 42 more
Steps to Reproduce
This was replicated in the GCS environment;
On the source system two simple text properties called DemoProp1 and DemoProp2 were created.
Next create a section called DemoSection1. And after saving the section perform a “Save As” and created a Circumstanced version of this section based on DemoProp1
Then creating another section called DemoSection2 and this time created a Circumstanced version based on the DemoProp2 property.
This should have added the two columns DemoProp1 and DemoProp2 to the PR_INDEX_CIRCUMSTANCE_DEF table.
If you don't have direct access to the database then you can also verify this by building an activity with the following details: -
And when you run the activity this should show the two new columns.
Next create the application zip using a Product rule which only contains the above ruleset and generated the product zip file.
When attempting to import this zip file onto a new system, the problem was occurring.
A defect in Pegasystems’ code or rules.
0% found this useful