Skip to main content

Highlight Row in Interactive Report

Recently I encountered a question on the OTN Forum about "How to Highlight a Current Row in an Interactive Report". For a regular report that kind of highlighting is a built-in functionality in the template, but an IR doesn't have a (editable) template (could be a nice enhancement for a future version though!). But you can override the styles used by an IR, by adding some STYLE tags in the Page HTML Header. First take a look at the on-line demo. You can click the [Edit] button to see the highlighting in action.

So how do we achieve that:
First we need to add a function call to the [Edit] link/button in the IR: Add "onclick=highLight(this);" to the Link Attributes property of the Link Column. This click calls a "highLight" function, defined in the Page HTML Header:

function highLight( pThis ){
$('td').removeClass('current');
$(pThis).parent().parent().children().addClass('current') ;
var empno = $(pThis).parent().next().html();
$s('P36_CUR_EMP', empno);
refreshReport( empno, 'P36_CUR_EMP' );
}
The "refreshReport" is a wrapper for some (standard) APEX functions to execute a Partial Page Refresh of the detail region on the right side of the page. The rest of the code is some jQuery stuff, first do a clean up to remove all "current" classes from the TD-tags - to "un-highlight" a previous selection - and subsequently add that class to all TD's in the current TR.

Next define a "current" style to your own taste. In this example I used:

.current
{
background : transparent url(#WORKSPACE_IMAGES#row-over.gif) repeat-x scroll 0 0 !important;
border-bottom : 1px solid red !important;
border-top : 1px solid red !important;
}
I also tweaked the standard "apexir_WORKSHEET_DATA" styles a bit to get a hover effect:

.apexir_WORKSHEET_DATA tr:hover {
background:#EFEFEF url(#WORKSPACE_IMAGES#row-over.gif) repeat-x scroll left top;
}
- and did some other restyling on the look-and-feel as well - but that's about it!

Comments

Stew said…
Roel,

That's pretty cool!

I also like your use of the IR for navigation while showing the detail on the right. I hadn't thought of that.

Thanks for sharing,

Stew
Anonymous said…
can you explain where do you do the style change?
Roel said…
The link has an attribute : onclick=highLight(this);
That will change the style using that javascript function.
Vamshi said…
refreshReport( empno, 'P36_CUR_EMP' );

I have multiple regions in a page how will this function know which region to refresh ?
Roel said…
Because it takes the current item as a starting point. Then it "moves up" to the current row and highlights it.
Vamshi said…
Could you please tell me the query of Emp Details Table ?

and when I try to produce what you said. I get :7777/pls/apex/f?p=102:9:401723411567861:::::#

and you application gets http://apex.oracle.com/pls/otn/f?p=41715:36:2560338678771080#

Do you know if im doing anything wrong ?
Roel said…
The query for the Emp Details table is:
SELECT EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO
FROM EMP
WHERE EMPNO = :P36_CUR_EMP
AND :P36_CUR_EMP IS NOT NULL
UNION
SELECT TO_NUMBER(NULL)
, TO_CHAR(NULL)
, TO_CHAR(NULL)
, TO_NUMBER(NULL)
, TO_DATE(NULL)
, TO_NUMBER(NULL)
, TO_NUMBER(NULL)
, TO_NUMBER(NULL)
FROM DUAL
WHERE :P36_CUR_EMP IS NULL

The code for the refreshReport function is:
function refreshReport(pValue, pField)
{ // Refresh this region with the new pValue for the pField
// var region=$v('P0_REGION_ID');
var region='R3259408924885046712';
var link='f?p='+ $v('pFlowId') +':'+ $v('pFlowStepId')+':' + $v('pInstance')+ '::::'+ pField+':'+ pValue;
html_PPR_Report_Page( this, region, link );
}
Stefan said…
where can i change the CSS .apexir_WORKSHEET_DATA tr:hover?
Roel said…
@Stefan,
There are more options, but you can add an inline STYLE on the page with <STYLE> and </STYLE> in the Page HTML Header.

Popular posts from this blog

Filtering in the APEX Interactive Grid

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 old Employ

apex_application.g_f0x array processing in Oracle 12

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

Stop using validations for checking constraints !

 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