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!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

apex5, null value in tree title makes developer toolbar disappear

PaavoJun 17 2015 — edited Jun 20 2015

Hi

With e.g. tree query:

select case when connect_by_isleaf = 1 then 0

            when level = 1             then 1

            else                           -1

       end as status,

       level,

       (CASE WHEN "ENAME" = 'KING' THEN null ELSE "ENAME" END) as title, -- null value is evil

       null as icon,

       "EMPNO" as value,

       null as tooltip,

       null as link

from "#OWNER#"."EMP"

start with "MGR" is null

connect by prior "EMPNO" = "MGR"

order siblings by "ENAME"

The developer toolbar disappears when there is null value in the Title. This is very very hard to detect problem.

https://apex.oracle.com

workspace: imagetest_ws

user: guru

pass: meditation

app: imgtst

page: 12

Rgrds Paavo

This post has been answered by John Snyders-Oracle on Jun 17 2015
Jump to Answer

Comments

Timo Hahn

How about adding a global button to the declarative component which you can use to notify the page to refresh. The general implementation can be found here http://www.oracle.com/technetwork/developer-tools/adf/learnmore/24-generic-toolbar-component-169163.pdf

You add an actionListener to the declarative component which you pass from the outside. When you need to refresh the page you call this listener from inside the declarative component.

Timo

SanjeevChauhan
Answer

If you want to refresh complete page, you can remove partialSubmit=true from button itself. That will make full page refresh. Yes its not a good practice as you are unnecessary refreshing all UI components.

If you want selectively refresh few UI components then you definitely tell ADF, which are those components. The simplest approach is individual components provide partialTrigger pointing to button.

If you don't want that then, I would suggest find a common parent component for all your tables. Set its partialTrigger pointing to button.

Thanks

Sanjeev

Marked as Answer by Robert Šajina · Sep 27 2020
Robert Šajina

Hi Timo,
Thank you for your reply.
I had a similar idea, to add a button outside of declarative component and somehow call it. Perhaps it is the best idea to move whole toolbar outside panel collection and somehow make it look that its inside panel collection

Where would that actionListener point to? would we be required to add a button to every page?

Robert

Robert Šajina

Hi SanjeevChauhan,

I have tried to remove the partialSubmit property (set it to false) but it doesn't do anything. I just need to refresh the next root component, and in our case that is <af:region>.

We are trying to avoid setting partial triggers to components as its to much work, and will require more work if something changes on declarative component.

Update:

I have tried to set partial triggers of a common parent(af: region) programmatically to id of a panel collection(panel collection is refreshed every time a button is pressed) and it works very well.
Now i just need  find a place/method that isn't called too many times, to add partialtriggers to af:region. If i manage to do it, i think we will keep this approach.

Robert

1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jul 18 2015
Added on Jun 17 2015
2 comments
508 views