com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference .pyID is not valid.
Hi All,
We've been getting the above error is production quite a lot, currently 136 occurrences today alone.
I've found SA https://community.pega.com/support/support-articles/section-execution-error-while-activating-virtual-grid which is exactly the error we are getting :-
Created Dump File expandStreamfmudttjjit.dat due to The reference .pyID is not valid. Reason: .pyID is mapped to class ABC-CAS-FS-Work-Svc, which is not the primary class of the list: ABC-FW-FS-Work; must specify a group name in mapping
But unlike the SA we are not using a custom activity to load the results. We are using a datapage populated from a report definition.
Any ideas how we fix this? Also of note, I've yet to recreate the issue in DEV, even though we have seen this error in DEV. The worst kind of problem.
Thanks
Craig
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
US
What version are you using? I found a similar issue reported on 7.2.2 that was fixed in 7.4.
In that case, the issue occurred when a combination of all the below things happened:
1) A Report Definition is defined on a framework class and is returning data from implementation class (because of the use Implementation class option available in Data Access tab)
2) A Data Page is sourced from the Report Definition referred to in first point. The Data Page is defined on framework class and is editable.
3) Passivation and activation of the Data Page in the second point occurs.
The issue did not happen if the Report Definition was not returning implementation results or if the Data Page was read only.
If you are on a version prior to 7.4, you could try making the Data Page read only until you can update to a later release.
Virgin Media
GB
Hi Carissa,
I'm unable to recreate this issue in DEV thus far, so i can't really check whether your suggested solution works.
I have created the error in DEV but I do not know under what circumstances the error is produced.
We are running Pega 7.3.1.
Thanks
Craig