My Oracle Support Banner

<af:query> Component's Filtering Not Working As Expected For Fields With LOV (Doc ID 2612092.1)

Last updated on FEBRUARY 17, 2021

Applies to:

Oracle JDeveloper - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On :  12.2.1.3.0 version, ADF UI (Faces, ADF Mobile, Swing, Desktop Integration)

An ADF application has a page with an <af:table> component with sorting and filtering enabled. The table is based on an Entity Object which corresponding View Object has List Of Values (LOV) defined on its attributes and the corresponding <af:column>s have attribute "FilterFeatures" set to "caseInsensitive" to bypass model-driven case-sensitivity and force case insensitive filtering mode. The LOV has "Default List Type" set to "Input Text with List of Values" or "Combo Box with List of Values". One of the View Object attributes has "Auto Submit" set to "false" in its "UI Hints" while the other has the "Auto Submit" set to "true".

ACTUAL BEHAVIOR
---------------
When searching the table from the "Search" region above the table using the af:query component, if the search is performed by using "Equals" operator on fields with LOV and if the searched value is not existing in the table, one of the following behaviors is observed:
- if the searched field has "Auto Submit" set to "true", the LOV popup saying "No rows to display" appears and vanishes immediately;
- if the searched field has "Auto Submit" set to "false", a validation error popup appears close to the search field.

EXPECTED BEHAVIOR
-----------------------
Since there are no matching values, "no rows to display" should be response.

Changes

 

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.