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

1 Voters

Enhance Popup LOV "Manual Entry" with Declarative Resolution on Lost Focus

devnetcsharp75 Public
· Feb 17 2026

Idea Summary
Enhance Popup LOV "Manual Entry" with Declarative Resolution on Lost Focus 

(Oracle Forms-like Experience)
 

Use Case
High-Speed Keyboard Data Entry in Financial & ERP Systems
In professional accounting and ERP applications (especially those migrating from Oracle Forms), speed is the top priority. Accountants memorize "Account Codes" (Return Values) and expect a "Keyboard-only" workflow.
The Problem: Currently, the Popup LOV forces users to break their flow. They must either use the mouse to open a modal search window or enable "Manual Entry." However, with "Manual Entry" enabled, typing a code like 181 (the Return Value) and pressing Tab (Lost Focus) does not visually resolve the name (the Display Value). The user gets no visual confirmation, and the developer is currently forced to write redundant Dynamic Actions for every single item to fetch the Display Value manually.

Preferred Solution (Optional)
Implement a Declarative "Resolve on Lost Focus" Property:
We propose enhancing the Popup LOV by adding a built-in setting that mimics the Post-Text-Item trigger logic from Oracle Forms:
Auto-Mapping (On Blur): When a user types a value manually and leaves the field (Lost Focus / Blur), the component should automatically perform a background lookup against the Return Value of the associated Shared Component LOV.
Instant Visual Confirmation: If a single match is found, the UI should immediately update to show the Display Value (e.g., "181 - Main Bank Account") while maintaining the Return Value (181) in the session state.
Smart Fallback: If the entered value is not found, the system should either show a validation error or automatically open the Popup search dialog for the user to pick the correct record.

Business Value:

This feature eliminates the need for modal windows and removes the burden of manual coding (Workarounds) from the developer. It provides the high-efficiency, reliable data entry experience required for complex financial systems, making APEX the ideal destination for Oracle Forms migrations

This is a great idea! You can already achieve this in APEX today with a slightly different approach.

Comments

Comments

  • vincent morneau Admin OP 6 months ago

    Have you tried the Select One item type? Seems like its blur behavior is closer to your expectations.

  • devnetcsharp75 OP 6 months ago

    @vincent morneau 

    Thanks for response 
    I don't know if i over explain the idea and get misunderstood
    actually i am talking about pop up Lov with Interactive Grid 
    other options like Text Field With AutoComplete is not an option
    in accounting system the chart of account is the heart of the system and its just code and name 
    the Accountants heavily depend on Code ..
    e.g. desging  Journal Entry Form requier code and the name
    so the best option is Popup LOV "Manual Entry"  but currently it lack many features 
    that's why i said Enhance Popup Lov Manual Entry

  • vincent morneau Admin OP 6 months ago

    Our course of action is that APEX should support newer LOV based items (select one many) in IG. Then this wouldn't be an issue. There is greater change of having this actioned than extending the popup LOV blur behavior.

  • devnetcsharp75 OP 11 days ago

    @vincent morneau 
    Hi APEX Development Team,

    I am writing back regarding your previous comment on this idea. You mentioned that the team’s course of action was to natively support the newer LOV-based items (Select One / Select Many) inside the Interactive Grid (IG) rather than extending the old Popup LOV blur behavior.

    We are now on APEX 26.1, and unfortunately, this critical capability is still nowhere to be found.

    As developers building massive, business-critical ERP systems, this is a major roadblock for us. We are migrating corporate users from high-performance Desktop applications (like Oracle Forms / .NET) to the web. For these users, an efficient, fast, keyboard-driven UI/UX is not a luxury—it is an absolute necessity.

    While we appreciate all the marketing-heavy features and AI capabilities introduced recently, basic data-entry components within the Interactive Grid shouldn't be neglected. Relying on the legacy Popup LOV behavior or turning to third-party plugins is an unsustainable workaround for modern enterprise applications.

    Could the team please provide a transparent update on the roadmap for this feature? When can we honestly expect native Select One and Select Many support within the Interactive Grid?

    Thank you for your continuous efforts, and we hope to see this actioned soon."