Skip to main content

Returning a value by clicking on a row

Image
By
In my previous post I showed a generic multi column LOV Report. One withdrawal was that the user has to click the first column to pass the selected value back to the calling form. It would be much nicer if you could click anywhere on the row, wouldn't it? To pass back a value you (used to) create a Named Column Report, but that is much too static.
By adding onclick="javascript:passBack( $(this).children('td:first-child').html() );" to the TR tag in the Before-Each- Row region you can click anywhere in the row and that will pass the value of the first column back to the calling page. Looks much nicer huh?
But (ofcourse) you need to install jQuery first....
Labels:

Comments

Stew said…
typo alert: "but that is much to static." should be "but that is much too static."

Rats, you got me really excited because I wanted this sort of functionality (click entire row) in the app I'm working on right now. Sadly, it looks like all roads (to cool web apps) lead back to jquery...

[sigh]
6:58 pm
Roel said…
@Stew. Thanks for the typo alert.I corrected the post.
And jQuery is not that scary as it might look at first sight. With just some simple statements you can really add some coollness to the look and feel of your app. Just dive in to it!
9:22 am
Stew said…
Roel,

I'm not afraid of learning and using jquery. I just can't get my DBAs to install it, mostly because they have other priorities
1:26 pm
Roel said…
Stew,
You don't need a DBA for this...just upload jQuery as a static file, reference it in your template, Page 0 or specific page and you're done!
9:25 am
Stew said…
True enough. I just thought the performance would suck because jquery wouldn't be cached, so it would get loaded each time.
1:14 pm
Post a Comment

Popular posts from this blog

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

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

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