Skip to main 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:
  1. 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.
  2. 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 worse) while you were working on page 3 of your report, it gets refreshed and your are back on square 1. There are some work arounds (like keeping the offset before refresh and returning to that position after refresh) and plugins that should keep the user on the same page.
But since Interactive Grid we have the option to refresh just one or more records! And to use that feature to update the currently selected row(s), you only need two lines of JavaScript:

var myGrid = apex.region( <regionid> )
             .widget()
             .interactiveGrid("getViews")
             .grid;
myGrid.model.fetchRecords( myGrid.getSelectedRecords() );

The first line defines the IG object, the second line is using the getSelectedRecords method to get the currently selected record(s) and passes these on to the fetchRecords method. The effect is awesome, as the page stays exactly what and where it was - so no scrolling etc - and you see only the data change. Even the "current" selection stays in place.
You only need to think about what should happen when the record is deleted (from the database or from the result set of your query) by your action....


And to make it even easier to use - and eventually adapt for future enhancements, you should create a simple Dynamic Action plugin. Or download it from here.


Post a Comment

Popular posts from this blog

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …