Question
Report Definition filter incorrectly changed to equals
I have built a Report Definition rule. In it there is a filter on surname. The business requirement is for the surname to a) be matched by "Starts with" to allow for partial searches, and b) that it is case-insensitive.
- When I set the filter to be "Cust.Surname Starts with Param.Surname" it works fine.
- When I set the filter to be "Upper case version of [Cust.Surname] Is equal Upper case version of [Param.Surname]" it works fine.
- When I set the filter to be "Upper case version of [Cust.Surname] Starts with Upper case version of [Param.Surname]" it builds the SQL to use "=" instead of "LIKE", i.e.:
...AND UPPER("Cust".SURNAME) = UPPER(? ) AND...
Please can someone confirm if there is a work around for this, or a hotfix? Or is this functionality not currently supported?
Many thanks,
Mike.
Thank you Sents. I have used the "ignore case" option as a workaround so my functionality issue is resolved.
Please can you (or someone in the appropriate team) confirm when the PRPC help documentation will be updated to include this information?
Many thanks again,
Mike.
Hi Michael,
This is something that has to be done from the GCS end.
Lochana,
Could you please take care of this.
Thanks Sathish and Mike!
I will raise it intenally to the documentation team and add in the request item details to the original post!
Regards,
Lochan | Community Moderator | Pegasystems Inc.
Accepted Solution
This is already documented in this support article - https://pdn.pega.com/support-articles/function-not-working-properly-report-definition-filter
Thanks Rajiv!
I was about to respond with that! You beat me to it :)
Since this is an expected bahvior, I have also raised a bug with the PRPC documentation team, in case they think this should go into the Help doc!
Regards,
Lochan | Community Moderator | Pegasystems Inc.
Thank you, everyone. This known behavior will be documented in the Report Definition rule form Help in the next release of Pega 7 Platform.
This query was earlier raised in the mesh forum as part of an SR and this is the response we received,
This is the expected behaviour. If you use a function in RHS of a filter condition, the filter operand is treated as equal. This is because if a literal was provided in RHS, we automatically add wildcards based on the operand type. But since a function has been used in RHS, we cannot add the wildcards and thus change it to equals.