Skip to main content

Creating dynamic multi column LOV's in APEX

Image
By

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

Unknown said…
That was really cool!
2:33 pm
Stew said…
Very nice!

I've requested our DBAs install jquery, but it's low on their priority list. Nice work with it.
5:43 pm
Louis-Guillaume said…
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.
6:12 pm
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.
12:34 pm
Anonymous said…
can any one demonstrate this multicolumn lov with code
3:36 pm
Roel said…
@Anonymous
Did you look at the live example on http://apex.oracle.com/pls/otn/f?p=41715:15 ??
4:58 pm
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!!
3:03 pm
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.
5:30 pm
Unknown said…
That is nice. Is it also possible to, like in 'good old forms', validate the entered value against the LOV?
9:37 am
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
9:11 am
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)
9:14 am
Anonymous said…
the link to the demo live desn't work. I have

ORA-01403: no data found
1:47 pm
Roel said…
@Anonymous : demo works again (someone had deleted my demo data...)
5:57 pm
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
12:26 am
Roel 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.
1:12 pm
Post a Comment

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

By
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 ...
Post a Comment
Read more

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good o...
1 comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...
Post a Comment
Read more