Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

DataPage Loopup is not returning the Results in Pega 7.1.9



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


.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. 


Apply HFix-27000.

Rules changed:- 



Published May 14, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us