By default, Pega adds the UPPER function to string properties used in filter conditions to make the search case-insensitive. However, this can slow down the filtering process, especially when dealing with large amounts of data. To avoid the UPPER function, you can modify the filter condition to use a case-insensitive search operator instead.
For example, instead of using the "LIKE" operator, you can use the "CONTAINS (CI)" operator to perform a case-insensitive search. The resulting filter condition would look like this:
"WL"."pxAssignedUserName" CONTAINS (CI) @P167
This will perform a case-insensitive search without the need for the UPPER function.
Alternatively, you can modify the report definition to use a custom SQL query that doesn't use the UPPER function. To do this, you can use the "Edit SQL" option in the report definition and modify the SQL query to remove the UPPER function.
Keep in mind that removing the UPPER function may make the search case-sensitive, which may not be desired in some cases. Also, it's important to thoroughly test any changes to the filtering process to ensure that they don't have any unintended side effects.
Posted: 9 months ago
Posted: 28 Feb 2023 10:48 EST
Abikash Kumar Sharma (AbikashKumarS16695091)