Table Filtering Not Working As Expected For LOV-based Attributes
(Doc ID 2552518.1)
Last updated on FEBRUARY 16, 2021
Applies to:Oracle JDeveloper - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Table filtering not working as expected
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 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".
When filtering on the column having "Auto Submit" set to "false", if the value entered in the filter field does not match exactly one of the values in the table, the entire table entries are listed as such, no matter if the entered value is a total or partial mismatch.
When filtering on the column having "Auto Submit" set to "true", if the value entered in the filter input text field is just a partial match of an entry in the table, but in a different case, the "FilterFeatures" set to "caseInsensitive" is not honored for that field and you will see a LOV popup saying "No rows to display" appears, no matter if the entered value is a total or partial mismatch.
When filtering a column in case of partial match, the matching values should be listed in the table, no matter if the match is partial and in a different case. If there are no matching values, "no data to display" should be displayed in the table.
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