Skip to main content

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 Employees table - and add a Static ID to the Grid region : "emp". We will use the "addFilter" method to do the trick.
So, run the Page, open the Developer Toolbar of your browser and type into the console:

apex.region("emp").call("addFilter", 
                       { type       : "column" 
                       , columnType : "column" 
                       , columnName : "LAST_NAME" 
                       , operator   : "EQ" 
                       , value : "King" 
                       }); 
       
This will add a filter to your report.
Now you can add this snippet of JavaScript to a Dynamic Action that runs on Page Load. Refresh the Page and the filter is automagically applied. Woohoo. Refresh the Page again and the filter is applied. Twice. Bummer.
So before we apply a filter on a column, we need to delete existing filters on that column first. There is another method "deleteFilter", but instead of a columnName, that needs a columnId as a parameter. So how do we get the colunnId? A third method comes to the rescue : "getFilters".
Calling apex.region("emp").call("getFilters")will return an array of filter objects. Alas columnName is not one of the elements. Thus we have to figure out what the ID is of the column we're using in our filter (LAST_NAME in our example). For that information we have to dig into the model:
apex.region("emp").call("getViews").grid.modelColumns["LAST_NAME"].id; returns that id (eg 34282803428196769095).
We can use this Id to loop through our filter objects and delete the filter that matches that Id:
var vRegion = apex.region("emp");
var vFilters = vRegion.call( "getFilters" );
var vFilterColId = vRegion.call("getViews").grid.modelColumns["LAST_NAME"].id;
for ( var i in vFilters ){
     if ( vFilters[i].columnId == vFilterColId ){
       vRegion.call( "deleteFilter", vFilters[i].id );
     }  
    }   
You can see the addFilter and deleteFilter in action here on apex.oracle.com.

Now you can use this code to fire an "autoFilter" when a certain Item (on Page 0) has a value and to delete a filter when that Item has no value. You have to make sure to set that Item to a value whenever it makes sense. For instance when opening a detail page, after querying or clicking on a button or link. You also have to create a way to unset that Item ... most likely when clicking on the "delete Filter" icon (that has a jQuery selector of  "button.a-IG-button--remove").

There's a little plugin (search for manageFilter on apex.world, or go to GitHub) that can contains this code and can help you started using this stuff.

But be aware ... the methods mentioned above and that are used in the plugin are NOT DOCUMENTED. Looking in the widget.interactiveGrid.js file you will see :
/*** FOR INTERNAL USE ONLY: Subject to change in the future, please do not use! ***/

So although it might work now, there is zero guarantee it will work after your next upgrade!

Comments

Ali Saleh said…
So thanks for this plugin
i will start use and i will give you feedback

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