Thanks for the info. I have been able to reproduce the issue, both on your page and a local example. I will file a bug and update the thread with details.
Thanks to both, and apologies to Pavel for not picking up on that thread sooner. I have now filed bug #25974131 to track this.
thank you very much for taking care of this issue. No need to apologize, APEX 5.1 came up with a lot of new features, so I think there was quite a lot of issues to solve with higher priority. First things first.
I can't seem to find any more information about this bug number.
Do you know the status of this issue?
Any workarounds available ?
This bug is now scheduled for the 5.1.3 patch I'm afraid. And unfortunately there is currently no good workaround either, other than to avoid this kind of external filtering mechanism and instead use the native filtering support provided by IG.
Sorry I can't provide a better answer at this time.
Could you please be more explicit when indicating that one could use the native filtering support provided by IG? If we don't want the user ever to see the explicit filter, is that possible?
I got past this error by using a SAVE button with Action set to "Define by Dynamic Action" and Database Action "SQL UPDATE action". I used this workaround on Apex version 5.1.2.00.09
button properties for a button called "save_fix":
Action "Defined by Dynamic Action"
onclick dynamic event for button called "save_fix":
plsql code for IG -Auto Row Processing(DML):
when 'C' then
insert into igcb_tasks ( LIST, SEQ ,"TASK", DESCRIPTION, DONE )
values ( :LIST, :SEQ ,:TASK, :DESCRIPTION, :DONE )
returning rowid into :ROWID;
when 'U' then
set LIST = :LIST,
SEQ = :SEQ,
"TASK" = :TASK,
DESCRIPTION = :DESCRIPTION,
DONE = :DONE
where rowid = :ROWID;
when 'D' then
where rowid = :ROWID;
There is a workaround for this that can be found in the IG Cookbook (rev 2). Download link here APEX IG Cookbook Update – HardLikeSoftware
The general idea is to use an extra page item that is submitted with the IG that is set to non null value only when the IG is saved. The SQL is modified so the extra page item lets all rows through.
From my example:
where list = :P11_TASK_LIST and (
( :P11_SHOW_COMPLETED = 'Y' or DONE = 'N')
:P11_SAVING is not null
Hopefully in the future this workaround won't be needed.
Thanks you John for your efforts!
I like to call this kind of fixes as the dirty ones.
Fortunately, I could fix this bug in one of my apps with validations that don't allow user to add value that doesn't meet the filter criteria. It was ok for my case and my users.
But after updating how can u refreshed the current report?
The tables come from the Sample Interactive Grids app. You need to install that first. The first page of IG Cookbook explains that.