Skip to main content

Alternating Row Colors in Interactive Report

In APEX, using an 'old-fashioned' report, you can create alternating row colors out of the box. But when you want to use the Interactive Report (IR) features, you can't do that anymore. But some people still have that need, according to this question on the Forum.
The main problem is that you can filter and re-order the resultset on the fly, so you can't define the coloring using the onload method of the page, because that's only fired once.
But when you have a Link Column in your report you can use the onload event of the image in that link :
<img src="#IMAGE_PREFIX#edit.gif" alt="" onLoad="Alternate(this);">
And define in your Page HTML Header:



You can see the colorful result here: http://apex.oracle.com/pls/otn/f?p=ROEL:ALTERROW

Comments

Thanks for the example Roel. It was very helpful.

One thing that didn't work for me was the line:

$(pThis).parent().parent().parent().addClass(lastColor);

I got an error that said "$ is not defined."

I had to use this line instead:
pThis.parentNode.parentNode.parentNode.className = "even";

Thanks Again,

Martin
Roel said…
Hi Martin,
I forgot to tell I use jQuery - I get so used to it I don't even notice it anymore - , and these are jQuery functions.
Roel
Algis said…
Hi Roel,
Thanks for all your examples, they are great!
Have you tried this Row Colors functionality with IE e.g. 6.0?
It works fine in Firefox 3.0 but I can't successfully use with IE :(

Best regards,
Algis
This comment has been removed by the author.
hi ,
i m new to apex and i m developing small application in apex ... in this application i want to have alternating row colors .. can u explain this in a broad way ... it might helpful for peoples like me who starting to study apex..
Thanxs in advance,
ram

Popular posts from this blog

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

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...

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 wors...

APEX ReadOnly Pages - The easy way

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...