How to get 'Look up Records' case insensitive

[Andreas Cierpka]

Unfortunately we do have mixed cases in our tables. When starting the service catalog ordering we ask the user for input. Just as an example the phase (PRD). What happened that we do get the value from ServiceNow discovery from tags. These values can now be prd or Prd ...

Is there a way in flow designer when doing the 'Look up Records' having this case insensitive?

 

[Ankur Bawiskar]

Hi,

GlideRecord queries are case insensitive.

Are you saying Look up records is case sensitive?

You can try to use OR condition and check for other case as well.

Regards
Ankur

[Andreas Cierpka]

Maybe some more details on the way it's currently organized. At the moment ServiceNow discovery run and updated the assets in the ServiceNow CMDB corresponding table:

In flow designer I do have the 'look up records' step




When running the flow I do get the counter = 1 because of the input done for the catalog item request.

I would like to be independent of the catalog item input value and get all possible matches back. In this case example the count should be "2". 

[Andreas Cierpka]

Let me provide you with more details. I do have the following assets in ServiceNow CMDB after discovery run.

The key information is in column 'Peak'.

My flow is going to take the user input from service catalog item and does a 'Loop Up Records'.

as mentioned the input parameters are taken from the user input when requesting the item. The 'Look Up Records' is going to return only the matching item.



As there is only one exact matching item the count is '1'. As I neither have influence on the value which is put into the catalog item request nor in the ServiceNow CMDB I would need a possibility where I would get the count = 2 back.