Skip to main content

Alternating Row Colors in Interactive Report

By
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
Labels:

Comments

West Michigan Gardener said…
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
11:31 pm
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
8:58 am
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
10:51 pm
Ramapandian Jayaraman said…
This comment has been removed by the author.
8:17 am
Ramapandian Jayaraman said…
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
8:17 am
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