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:

                       { 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 = "getFilters" );
var vFilterColId ="getViews").grid.modelColumns["LAST_NAME"].id;
for ( var i in vFilters ){
     if ( vFilters[i].columnId == vFilterColId ){ "deleteFilter", vFilters[i].id );
You can see the addFilter and deleteFilter in action here on

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, 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!


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

Popular posts from this blog

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

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