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

Invalid expression or reference ERROR coming on screen

SA-7257

Summary



Account is using PegaKYC 6.2.5 on top of PRPC 6.2SP2ML1.
Whenever user tries to execute a ReportDefinition by applying the filters, the error is displayed on the screen.

Caused by: com.pega.pegarules.pub.runtime.IndeterminateConditionalException: ** Invalid expression or reference: Multiple suitable instances found [seeking] @(null:null).getPropertyValue(ClipboardPage,String) [possible candidate functions are] @(PegaKYC:KYCUtils).getPropertyValue(ClipboardPage,String) @(Pega-ProCom:RuleManagement).getPropertyValue(ClipboardPage,String)


Error Messages



Error on screen:

** Invalid expression or reference: Multiple suitable instances found [seeking] @(null:null).getPropertyValue(ClipboardPage,String) [possible candidate functions are] @(PegaKYC:KYCUtils).getPropertyValue(ClipboardPage,String) @(Pega-ProCom:RuleManagement).getPropertyValue(ClipboardPage,String) SUGGESTION: Use full syntax for calling a function, Example- @(RuleSet:libraryname).functionname(arg1, arg2... argn) Rule-Utility-Function @.getPropertyValue(@pxGetParentPage(stepPage),"pzIsSummary") Invalid expression or reference: Operation "==" is not permitted on types: unknown and text ( @.getPropertyValue(@pxGetParentPage(stepPage),"pzIsSummary") == local.isUiSummary )


Steps to Reproduce



1. Create a report on PegaKYC application
2. Run the report by applying some filters and observe the error message displaying on screen


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules.
In PegaKYC framework, there is a getPropertyValue function present in KYCUtils library which is present in KYC ruleset. There is a same function with same name present in RuleManagement library present in ProCom ruleset.
When user tries to run the report by applying some filters, reRunReport activity will be called which uses this getPropertyValue function.
But system is confusing which version of this function need to consider at run time, as there are two functions available with same name.

Resolution



This issue is resolved by hotfix item HFIX-21224
As part of this hotfix, reRunReport activity is modified suchthat getPropertyValue function will be called along with Library
Eg: @(Pega-ProCom:RuleManagement).getPropertyValue(ClipboardPage,String)
 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

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.

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