Skip to main content

Creating dynamic multi column LOV's in APEX


The default LOV's in APEX are implemented as a pop-up window, with the restriction that you can only show one display value. This is sometimes just what you need, but mostly it is not sufficient. You can create a longer display value by concatenating strings, but that won't enhance the looks of your application. What you do need is an LOV with multiple columns, more or less something similar as the LOV's you can get in good old Oracle Forms.
You can create an LOV Page for every LOV that you need and create a button with a link to that page for any item, but than you'll end up with lots of pages. Wouldn't it be better to use a similar feature as APEX itself has: Define an LOV query and attach that to an item?


So I created two tables: LOV_ITEMS and LOV_DEFINITIONS. The first one holds a reference to the APEX Page Items and a reference to a LOV Definition. The last one contains the SQL Query that will be used in one generic 'LOV Page' to show a report that acts as an LOV. With some templating for the looks, jQuery to dynamically create the buttons with the links and some javascript (Ajax) to show and hide the LOV the result looks a lot better.

A live demo and more details are available here.

Comments

mhathi said…
That was really cool!
Stew said…
Very nice!

I've requested our DBAs install jquery, but it's low on their priority list. Nice work with it.
Nice demo!

Each time I open a LOV, 4 files get loaded:
apex_ns_3_1.js
apex_3_1.js
apex_get_3_1.js
apex_builder.js

I think you should remove the call for those files on your Page LOV Template. Load them once on your main page.
Anonymous said…
Great, it is very useful.

Do you know why if I enable the pagination schema with "Enable Partial Page Refresh" to yes I get an "undefined" message when I click to see next records ?

The standard javascript procedure should make a AJAX call and replace the HTML region content.

David.
Anonymous said…
can any one demonstrate this multicolumn lov with code
Roel said…
@Anonymous
Did you look at the live example on http://apex.oracle.com/pls/otn/f?p=41715:15 ??
Anonymous said…
Hi
I want a smiliar type of functionality in my application.Can
any one give me a demo of this in my workspace
wkp: oitoracle
uid: pavan9138@yahoo.co.in
pwd: $uguna

thanks in advance!!
Anonymous said…
Hi regarding the pb with the LOV pagination you can look:
http://forums.oracle.com/forums/thread.jspa?messageID=3313873&tstart=0#3313873

Regards,
David.
Maurice said…
That is nice. Is it also possible to, like in 'good old forms', validate the entered value against the LOV?
Anonymous said…
why doesn't this example work in IE 7. Give a Java script error
"Could not get the display property. invalid argument" line number points to gReturn =get.get() line in show LOV function
Roel said…
@Anonymous : From APEX 4 onward you'd better (easier) use the Skillbuilders Super LOV Plug-in (http://apex-plugin.com/oracle-apex-plugins/item-plugin/skillbuilders-super-lov_75.html)
Anonymous said…
the link to the demo live desn't work. I have

ORA-01403: no data found
Roel Hartman said…
@Anonymous : demo works again (someone had deleted my demo data...)
Anonymous said…
Hi..
But the demo contains only 1 column.. I want to know how you create multiple columns like the one shown above.. Pl give more details.
Thanks,
D
Roel Hartman said…
The right LOV's on Order and Product contain one column (the original ones). The left ones however contain 4 and 5 columns.
But I suggest that you use the SuperLOV plugin (see apex-plugins.com). Makes your live a lot easier.

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…