Skip to Main Content
Feature Request FR-2981
Product Area APIs
Status ROADMAP

23 Voters

Add public APIs to LOV components

ino.laurensse Public
· Feb 16 2023

Idea Summary
Create APIs to handle Shared Component or Inline LOV's in SQL or PL/SQL.

Use Case
Easily get LOV display value for a LOV return value (or the other way around) for a given Shared Component LOV or Inline page item LOV. 
Right now, for static values, you have to code it yourself, e.g.:

select display_value  
from apex_application_lov_entries  
where application_id = :app_id 
and list_of_values_name = 'COUNTRIES' 
and return_value = 'USA' 

For Dynamic LOVs it is practically impossible to use the stored SQL query in your own code.

Preferred Solution (Optional)
Expose useful functions in wwv_flow_lov (like get_shared_lov_id and get_lov_display_value) as public APIs.

This is currently on the roadmap for a future release of Oracle APEX.

Comments

Comments

  • vincent morneau Admin OP 2.4 years ago

    Hi @ino.laurensse ,

    There are pros and cons to exposing those wwv_flow_lov functions. Can you elaborate on the use cases for this so we can better evaluate the idea? Thanks!

  • ino.laurensse OP 2.4 years ago

    Hi @vincent morneau 

    Some cases: 

    • Run validations against the values in the LOV in PL/SQL. This is probably the most useful case, as Select List (LOV) values can easily be manipulated in the browser.
    • Use LOV display values directly in a query. E.g. if you have some kind of report in a PL/SQL region where you cannot map columns as “Plain text (based on LOV)”.
    • Using the LOV display values in an external reporting tool, like Jasper, PL/PDF.
  • ino.laurensse OP 2.3 years ago

    Another one I ran into again today: get the return value for a “Text with autocomplete” item.

  • marcelo osorio kosky OP 6 months ago

    100% agreed with Ino.

    • Avoid re-run the sqls to get the LOV Descriptions
    •  Store the description when you call external call (APIS)

    Regards,

    Marcelo