This content has been marked as final. Show 6 replies
We can't look without workspace name - or post LOV SQL
Im sorry, this is:
That's officially weird. If there is a problem I don't see it, but I've had my share of APEX gremlins this morning that required me to use a new item name to replace something that had been working previously...1 person found this helpful
Well, I agree, this was weird enough I just had to take a look. I could see the ajax firing twice for the select statements very odd.
Digging in your page template I noticed that you had commented out the #BOX_BODY# tag.
#BOX_BODY# is mandatory, so I put it back. I think you were able to fool APEX because you had it on the page, but it was all inside a comment.
<!-- <table class="tbl-body" cellspacing="0" cellpadding="0" border="0" summary=""> <tbody> <tr> <td class="tbl-main" width="100%">#REGION_POSITION_02##BOX_BODY#</td> <td class="tbl-sidebar">#REGION_POSITION_03#</td> </tr> </tbody> </table> -->
Anyways... I don't care to completely understand why the JS code that refreshes the selects was added twice to the page, but it's fixed now. :)
Just make sure you have your BOX_BODY tag in all your pages. Even if you don't want to use it. :)
Oh and FYI, the items don't need to be added to Page Items to Submit because the Cascade LOV Parent Item list already takes care of that.
From the help on the field +"You can then use those page items in the where clause of your "List of Values" SQL statement."+
Edited by: jrimblas on May 9, 2013 10:46 PM
I thought it was odd the test region didn't appear when I first created it.
That was me that added the page items to submit, last ditch attempt...
Jorge, thank you very much, I never thought about that.!