My Oracle Support Banner

LOV Not Searchable with % Wildcard When Using New LOV Definition in APEX 19.2 (Doc ID 2663204.1)

Last updated on FEBRUARY 18, 2021

Applies to:

Oracle Application Express (APEX) - Version 19.2 to 19.2
Information in this document applies to any platform.

Symptoms

A LOV is not searchable with % wildcard when using new LOV definition in APEX 19.2. 


To reproduce the problem: 

LOV 1:
Contains a Legacy SQL definition in the shared components.
The LOV is searchable with % - e.g.: '%<sometext>%' returns some rows

LOV 2:
Contains a new definition created with APEX 19.2 - same query as LOV 1.
LOV is not searchable with % - query '%<sometext> %' does not return any rows.
- This is the same search text used for LOV1. 

LOV 3:
Contains a SQL query in the item definition - same query as above.
LOV is searchable like LOV 1

In this case the LOV 1 and 3 are searchable but not the LOV 2. 

It works with LOV 3 - so we have to use the SQL query directly in the item definition and we are no longer able to use the shared component definition?



Changes

 A page item of type Popup LOV uses LIKE as search operator for Inline and Legacy Shared LOVs, but uses INSTR for newly defined Shared LOVs.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.