Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Hide Interactive Grid Column on Region Refresh

SteveQuinlivanMay 23 2022 — edited May 23 2022

Afternoon all,
I'm aware I can hide an Interactive Grid column on page submit / render using Server Side Conditions, but I'm wondering if it can be done via a refresh Dynamic action without having to re submit / render the whole page.
I have a Select List that when changed, triggers a refresh of an IG region and changes the displayed data.
I have a new requirement to hide certain columns in the IG when there is a particular value in the select list, and ideally to be able to do this smoothly / dynamically.
I'm using Apex 19.2.
As always any help greatly appreciated.
Regards

This post has been answered by SteveQuinlivan on May 23 2022
Jump to Answer

Comments

One alternative could be that there is a bug in the JNI code.  The use of the option ends up allowing the bug to impact the application space in a way that the OS detects it - and thus the SEGV.

Michaelt-Oracle

While a user level bug is certainly a possibility what's strange about this case is there are no user level threads making JNI calls at the time of the crash. We've also determined the crash occurs on OEL but not on Solaris Sparc, other platforms to be tested soon. The question here is simply if there are any known issues. My queries of bugdb did not yield any.

> there are no user level threads making JNI calls at the time of the crash.

Irrelevant.

SEGV occurs because the OS detected that the application did something bad.  That can occur any time once the bug occurs.  It might be immediately or hundreds of lines later.  For example if the code corrupts the native heap then the fault might not occur until the native heap manager attempts to compress the heap which can occur much later.

> We've also determined the crash occurs on OEL but not on Solaris Sparc

Different execution paths which means the potential for different behavior.  So in one case it does something the OS sees in the other it doesn't.

1 - 3

Post Details

Added on May 23 2022
1 comment
1,648 views