I've been asked to investigation errors that are occuring in our production environment since our upgrade from 7.2 to 7.31.
There are a lot of errors occurring daily with the title of this posting. Specifically this is the full error message :-
Caused by: com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference .pyWorkBasket is not valid. Reason: .pyWorkBasket is mapped to class Data-Admin-WorkBasket, which is not the primary class of the list: Data-Admin-Workbasket; must specify a group name in mapping
Seems to relate to a report definition from a datapage. Previous error to the one above is :-
Caused by: java.lang.RuntimeException: caught exception while expanding property pxResults on page D_WorkBasketsInWorkGroup_pa4357572887357862pz
This datapage is used to drive a dropdown component. The datapage is Structure = List , Object type = Data-Admin-Workbasket, Edit mode = Editable and Scope = Thread. Datasource is a report definition against class Data-Admin-WorkBasket. The report returns pyWorkBasket, pyWorkGroup and pyLabel. The dropdown component then uses .pyWorkBasket for the "Property for value" field and .pyLabel for the "Property for display text".
I have tried with dropdown control and giving the Data page source and I am able to get the values properly without any error in Rules log. So the 7.3.1 base PRPC code is working fine. It might be because of Framework (Customer Service).
So I would suggest you to first trace the Data Page and see whether you are getting any error. Also there are chances of corruption while upgrade. Then raise a SR with Pega GCS with tracer and error trace you are getting.
Thanks for the response, however I am not able to recreate this issue. I've ran the datapage I've also accessed the portal the same way as the users and I am not able to reproduce this issue. I have also ran the tracer and found nothing of interest in there either.
There have been over 50 occurrences of this issue on one of the production servers today alone. Different users, so it's definitely an issue, it's just I can't seem to recreate it.
Any other ideas?
I have managed to see this for myself once in production. Basically the section that is supposed to load when the user clicks on the heading of the layout group just simply doesn't load the section that contains the dropdown control. Refreshing this section corrects it. So it looks like an intermittent issue, but one that obviously the users are experiencing a lot.