Hello all,
We are retrieving a row data from Database using query entity.
In query filter we have a condition to get a row data.
Example
a!queryFilter(field: "name",operator: "includes",value: ri!status)
Database having status value as "awaiting_info" I need to get the row data irrespective of case sensitive like (ri!status= "awaiting_info" or "AWAITING_INFO" or "AWAITING_info" or "awaiting_INFO") .
On the "status" fields in the postgreSQL data base side applied the case_insensitive COLLATION .But wherever we have applied the case_insensitive COLLATION, those colums are not supporting the "include" operator from the query entity from Appian expression rule.
Any suggestion on this !!!
Discussion posts and replies are publicly visible
Hello Venkatesh Suram ,
Have you tried with "in" operator?
Yes "in" operator is working fine.
If you want to use include in the DB it is in lowerCase so in the value try using the lower() function it will work
Value:lower(ri! status)
Found this: https://docs.appian.com/suite/help/23.4/fnc_system_a_queryfilter.html#case-sensitivity-on-record-types-with-data-sync-enabled
But that does not directly answer your question.
I only use constant text values to store and check against such fields. That avoids this issue altogether.
--- A few minutes later ---
Did a small test with MariaDB. The "includes" operator performs a case insensitive search.
Conclusion: Open a support case and report this behavior. I would a similar behavior with PostgreSQL.
I have few use cases to search any text search OR any other operations as mentioned in the example. Ex: (ri!status= "awaiting_info" or "AWAITING_INFO" or "AWAITING_info" or "awaiting_INFO") . However it is just sample but trying to understand why appian "include" operator not working.
If there is an extra characters like spaces etc in the value "AWAITING_INFO" if your value has
" AWAITING_INFO" then it won't work if you use IN operator it will check the AWAITING_INFO neglect other characters.
Better to check appian documentation
Hi Venkatesh Suram I have did some testing using include operator, It is not an case sensitive search, it is returning the output irrespective of the case what you have entered in value, As said you can open a support for case for this behaviour