They are addictive
I've seen a video of a David Peake presentation about IGs where he warns that developers will be tempted to overuse them. It's true: once you've built a couple of IGs you are inclined to want to use them on every page instead of showing a report with an edit link. They are very slick and modern in appearance. But it's important to consider the users and whether the IG is the best interface for what they need to do.
They are very new
Like anything very new, they having teething troubles. I've raised a number of issues on the Oracle APEX forum where things don't seem to work quite as they I would expect, or found issues that others have already raised. These include:
- Issue with master-detail IG when master column is a select list (IGs are a lot happier with a hidden surrogate key or ROWID rather than a manipulable column as key)
- IG scroll-type pagination doesn't work in modal pages - you just get the first 40 rows returned.
- Editable IGs are too wide by default with columns scrolling off to the right.
A common thread here is that these questions often don't get answered. I think this is because there is only one person who might know the answer, and he is no doubt a very busy man!
Being new they are also somewhat scant on documentation.
They are complex to configure
Out of the box you can configure a few properties of an IG via the APEX Builder such as:
- Grid is editable or not
- Insert/Update/Delete operations allowed or not
- Toolbar is shown or not
- Save and Reset buttons are shown or not
- ... and several other things
I think that this complexity of configuration rather goes against the APEX principle of "low code", and very much hope that a lot more declarative control will be added in future versions of APEX. But I appreciate that's a pretty tall order and Rome wasn't built in a day!
They can be slow to load
Interactive Grids are a great and powerful addition to the APEX toolkit, a vast improvement over the old tabular forms. They should be used where they really add value, and not overused. Being very new, they have a few issues, are not well-documented (compared to the rest of APEX), and require some quite advanced coding (and a lot of Googling) to configure if the default behaviour is not what you need. I'm sure that by the time APEX 6.0 comes out they will be even better, and much easier to configure!