Table Filter For LOV Fields Reports An Error When The Value Entered In The Filter Has No Exact Match (Doc ID 2518818.1)

Last updated on APRIL 12, 2024

Applies to:

Symptoms

An ADF application has a page with a read-only component with sorting and filtering enabled. The table is based on an Entity Object which corresponding View Object has a List Of Values (LOV) defined on one of its attributes and the corresponding has 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".

ACTUAL BEHAVIOR
---------------
When filtering one of the columns, if the value entered in the filter input text field does not match one of the values in the table, a popup error appears. This happens even if the entered value matches partially one of the values in the table or even if there is an exact match except it is not written with the same case (i.e. "australia" instead of "Australia").

EXPECTED BEHAVIOR
-----------------------
When entering a value in the input text field of a filter for a column, no error is expected in whatever case: in case of no matches according to the above criteria, "No data to display" message should be shown.
Also, if the value matches, even if partially, a record with a case-insensitive criteria, the corresponding records are expected to be listed.

Changes

Cause

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