Question
Tata Consultancy Services
GB
Last activity: 14 Feb 2018 13:59 EST
pxObjClass is unmodifiable error in Pega 7.3
Hi All, We have upgraded our environment from Pega 6.2 SP1 to Pega 7.3 During the testing, we are getting the following error while running an existing datatransform. •The Flow Action post-processing activity PostSelectContact failed: The page or property RetrieveInvolvedPartyDetailsPage.retrieveInvolvedPartyDetailsRetrieveInvolvedPartyDetailsResult0.contactPreferences(1).contactPoints(1).pxObjClass is unmodifiable. Calling method: com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.put(String, ClipboardProperty, boolean, boolean, boolean) Details: existing property is reserved • The page or property RetrieveInvolvedPartyDetailsPage.retrieveInvolvedPartyDetailsRetrieveInvolvedPartyDetailsResult0.contactPreferences(1).contactPoints(1).pxObjClass is unmodifiable. Calling method: com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.put(String, ClipboardProperty, boolean, boolean, boolean) Details: existing property is reserved The interesting fact is that when turn on tracer and trace the same, the error is not happening. Without tracer, this exception is happening. It is a complete blocker for the application. Could you please help....... Thanks Vaisakh
***Edited by Moderator Marissa to update categories***
Pegasystems Inc.
US
Hi Vaisakh,
Kindly look into this article which might help you and let us know if it helps.
Regards
Mahesh
PEG
US
It really is critical that you let us know if the failure occurs during a Data Transform operation, or an Activity step. If an activity step, then Page-Change-Class should work for you.
If a Data Transform (you can tell from the complete stack trace), then as the Support Article states, there was a bug that sometimes affected setting the class in a Data Transform. A work around is provided, have you tried it? There also was a hotfix for this in the 7.2.2 release. You don't mention your release.
There were some hairy problems involving what happened during a page-copy or a page-merge. If you provide the complete stack trace, we can tell which of these several possibilities apply, if any.
Finally, if not a page-copy or merge, and if this is occurring in a Data Transform, if you change to instead using an Activity and then use a Page-Change-Class, that should resolve the problem.