This content has been marked as final. Show 10 replies
How have you defined the on change event so far?
Could you use a dynamic action that refreshes both regions?
I may be wrong, but I dont think a tree supports being refreshed via ppr/apexrefresh.
Some regions don't support it - but I have succeeded with trees recently in 4.2
Tried 2 ways
1. DA on Change event
Action : Refresh , Regions: <Tree Region>
2. SELECT LIST Attribute > Page Action when Value Changed > Submit Page
And they both worked?!
What is going on? What happened, didn't happen - and maybe what error message did you get?
What version of APEX?
I also tested two ways:
Dynamic action refresh region on click of button - no dice;
Run the following:
$('#blabla').trigger('apexrefresh') (where #blabla is the static id of tree region).
My mistake, I've checked out the application I built that tree page in.
The DA was to refresh a different region on selection of a tree node. I remember not being able to refresh the tree, but submission of the page (from the auto-complete textbox) worked no problem - page submitted, tree rendered relevant selection.
apologizes for incomplete sentence in my last post
I tried both the methods but to no avail
IR populates but the Tree does not get populate.
Session values contain correct values, which when passed in the tree sql separately, works fine.
Just that the Session value does not get to the Tree Region but only gets to the IR region.
As it stands now
SELECT LIST-------->>>Page Action when Value Changed : Submit Page
IR populates ---------------------------------Tree does not populate
Hope I am clear now
Can you re-produce an apex.oracle.com.
Using dyamic actions wont work, but I can't see why submitted the page wouldnt. Does the select list value get set when you check session state? Does the tree query reference that item correctly?
I am really sorry for the blunder ...
sql had > ORDER BY
APEX expected > ORDER SIBLINGS BY
NOW It works :) with only Page Action when Value Changed: Submit Page