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

case sensitive while search in ListView



Searches with ListView appear to be case-insensitive but searching the DB directly appears to be case-sensitive. 

When using the Ignore Case option in ListView, the search becomes case insensitive . However, PPRC gives the following warning while saving the Listview :

Caution - Performance

Case Insensitive search operation can adversely impact performance. To improve performance create functional index using UPPER() function on the columns that need case insensitive search

Error Messages

No output get generated

Steps to Reproduce

1. Mark the checkbox to use  Ignore Case option in ListView

Root Cause

This is an intended behavior. The PDN article explains on the correcting the warning messages.


PRPC OOTB Listview search is case sensitive, we need to use Ignore Case option in order to get case insensitive. PRPC gives a warning message for activating Ignore Case 

Please check the below PDN for correcting the warning message:

We can have a look at the extracts from ListView help on Ignore Case:

Select to cause runtime tests or comparisons of the Field value and the Value value to occur after the system converts both to uppercase. If selected, then at runtime "a" matches "A" and is less than "B".
Clear to cause tests of the Field value and the Value value to occur without case conversion. In this case, "a" is greater than "A" and also greater than "B"
CautionIn most cases, leave this box cleared. Select this box only when truly necessary to obtain the rows of the report:
  • If your PegaRULES database is hosted by Microsoft SQL Server, comparisons are alwayscase-insensitive, so selecting this box does not affect the report contents, but may add processing.
  • If your PegaRULES database is hosted by Oracle, IBM UDB or most other database vendor products, selecting this box may affect which rows appear in the report when values occur in mixed case. However, conversion to uppercase can significantly slow database processing.
  • Case conversion is meaningful only for properties of type TextIdentifier orPassword. Regardless of database software, case conversion is not needed for numbers, dates, or text that contains only uppercase or only lowercase characters.

Published January 31, 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