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

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

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

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more