InvalidReferenceException .pyRuleName
I am getting an error in our PEGA logs that reads:
(Commons_Data_Interface_.Action) INFO gbautilwas1.corp.bcbsal.org|XX.XX.XX.XX|SOAP|CGBACTI|Event|AgentCallNotification|AB6A8EA7934A1AF91FCAF24383BA5B810 - LogServiceInOutTime*Application:CC*ID:151641000006927*InTime:20160307T213925.282 GMT*OutTime:20160307T213925.300GMT*TimeDifference:18.0*Msg:ScreenPop2016-03-07 15:39:33,168 [ WebContainer : 12] ( rd.resolve.SqlReportResolver) ERROR gbautilwas1|gba10004548.corp.bcbsal.org - An error occured during resolving the report definition - InvalidReferenceException .pyRuleName Cannot use an unexposed property as there is no BLOB column for the class: Data-Rule-Locking com.pega.pegarules.data.internal.rd.reference.InvalidReferenceException: InvalidReferenceException .pyRuleName Cannot use an unexposed property as there is no BLOB column for the class: Data-Rule-Locking
I was looking up this error and found the PDN article 'https://pdn.pega.com/support-articles/invalidreferenceexception-post-cpm-713-upgrade'. We are on CPM 7.1.3 and PEGA 7.1.6. This article references an error message simliar, but no exactly like our error message. My question is, will the fix listed in the article also apply to our log file error message?
I am getting an error in our PEGA logs that reads:
(Commons_Data_Interface_.Action) INFO gbautilwas1.corp.bcbsal.org|XX.XX.XX.XX|SOAP|CGBACTI|Event|AgentCallNotification|AB6A8EA7934A1AF91FCAF24383BA5B810 - LogServiceInOutTime*Application:CC*ID:151641000006927*InTime:20160307T213925.282 GMT*OutTime:20160307T213925.300GMT*TimeDifference:18.0*Msg:ScreenPop2016-03-07 15:39:33,168 [ WebContainer : 12] ( rd.resolve.SqlReportResolver) ERROR gbautilwas1|gba10004548.corp.bcbsal.org - An error occured during resolving the report definition - InvalidReferenceException .pyRuleName Cannot use an unexposed property as there is no BLOB column for the class: Data-Rule-Locking com.pega.pegarules.data.internal.rd.reference.InvalidReferenceException: InvalidReferenceException .pyRuleName Cannot use an unexposed property as there is no BLOB column for the class: Data-Rule-Locking
I was looking up this error and found the PDN article 'https://pdn.pega.com/support-articles/invalidreferenceexception-post-cpm-713-upgrade'. We are on CPM 7.1.3 and PEGA 7.1.6. This article references an error message simliar, but no exactly like our error message. My question is, will the fix listed in the article also apply to our log file error message?
***Updated by Moderator: Marissa to remove proprietary information from post; moved from Product Support Community to Pega Customer Service***
***Updated by moderator: Maryrita to add Group Tag***
Pegasystems Inc.
IN
Hi Mark, The PDN post you referred explains about the CPM related data properties as need to remap the database table for few data classes after upgrade to CPM 713.
But your issue seems to be with PRPC OOB property .pyRuleName. In one of the report definiiton, it is trying to retrieve the .pyRuleName column from the DB table where the property is not optimized/existed.
As per my analysis, i could see that, Data-Rule-Locking is associated with pwbv4_rule_locking DB table. A column name called pyrulename is present in the DB table. Can you check whether the column is available in the above table.
Cahaba Gba
US
No, this is not a column in the table. The only columns in the table are:
PXOBJCLASS
PXINSNAME
PYCLASS
PXUPDATEDATETIME
PXUPDATEOPNAME
PXUPDATEOPERATOR
PYLABEL
PYRULESET
PYRULESETVERSION
PYCIRCUMSTANCEPROP
PXINSTANCELOCKEDBY
PZINSKEY