Support Article
DataPage Loopup is not returning the Results in Pega 7.1.9
Summary
While trying to source a Datapage with Lookup . "No records were found for the lookup with keys" is getting triggered and is displayed on the screen.
Error Messages
Error:
.BenefitSetTree.ChildItem(1).ChildItem(1).ChildItem(4): ** No records were found for the lookup with keys : {LOBOffering=Commercial; pyRunDataTransformOnError=; pyLookupClassName=Rule-HC-PCS-Benefit-Med; pyPageStructure=page; EffectiveDate=20150101T050000.000 GMT; ProductCategory=Medical; pyExecuteOnDataPage=true; Name=BEN-36-1459260483270; pyRuleSet=PegaHC-USA-PCS; pyPassCurrentParamPageForRespDT=; pyClassName=PegaPCS-HC-USA-Work; pyDefinitionKey=RULE-DECLARE-PAGES D_GETBENEFITBYCATEGORYANDKEY #20141215T154609.638 GMT; pySavedInPegaVersion=7.1.9; pyResDataTransform=}
Steps to Reproduce
Source Data page with lookup.This issue is reproducible when pyClassName itself is key while performing lookup.
Root Cause
While performing lookup, user fetch pyClassName from parameter and consider that as primary page class, which should be data page page class.
In this particular use case it is getting overridden as pyClassName itself is passed as parameter.
Solution is instead of using pyClassName from parameter page to depict primary page class, and Pega is going to use pxObjClass from parameter page, which is an actual data page class.
Resolution
Apply HFix-27000.
Rules changed:-
pxCallObjOpen
Published May 14, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.