Skip to Main Content
Feature Request FR-4275
Product Area Page Components
Status CLOSED

1 Voters

Automatically implement a restricted LOV in compliance with the constraint column

miguel.m.tavares Public · Feb 14 2025

Idea Summary
APEX could auto implement restricted LOV (List Of Values) in compliance with the column constraint specified in Data Model Tab

Use Case
A column table named CREDIT_RATING from table CREDIT_CLIENTS has a constraint that only allows the values (EXCELLENCE, GOOD, POOR). When APEX creates the User Interface it should automatically  implement a restricted LOV in compliance with the restricted values defined in the constraint column for that table. If we change the constraint in the Data Model it should automatic refresh the APEX front end user interface solution.

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is unlikely to make its way into APEX.

Comments

Comments

  • carsten.czarski APEX Team OP 3 weeks ago

    We discussed that idea, and we think it's not feasible to generate shared LOV entries in APEX from table constraints.

    • Table constraints are focused on data integrity; whereas shared LOVs are focused on the UI.
    • You cannot deduct LOV Display Values from database constraint values. Database constraints often use abbreviations or technical terms which one would not want to see in a UI.
    • Automatically refreshing a shared LOV from a changed constraint would require APEX to either create DDL triggers or to frequently scan the data dictionary for changed constraints - both options are typically not wanted on running database instances.

    All in all a UI List of Values is related to a database constraint, but at the end these are different things - so we would not want to tie these together in APEX.