LOV Fields Are Identified As "Component" On Error Validation When The Form Is Based Upon An <af:table> Component
(Doc ID 2894459.1)
Last updated on SEPTEMBER 23, 2023
Applies to:
Oracle JDeveloper - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
An ADF application has a page with an editable <af:table> component backed by a View Object and a button used to trigger the "CreateInsert" control.
One of the attributes of the View Object is marked as mandatory and has a LOV defined on it.
ACTUAL BEHAVIOR
---------------
At runtime, if the user creates a new record and does not enter any value for the field corresponding to the aforementioned attribute, the appearing error popup will label the attribute as "Component", making it hard for the user to determine which field in the row that error corresponds to in case there is more than one mandatory field missing.
EXPECTED BEHAVIOR
-----------------------
When the errors are reported they should identify the field by the label used and not by a generic string (like "Component").
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 |