Possible Bug in APEX 4.1 Tree Region

Hello Everybody,
I am developing an APEX application and want to add a navigation tree.
So I downloaded the Oracle packaged sample application "Sample Trees".
I created a tree region like the tree on page "Project Tracking" and realized that the lines at the left of the images were not visible in my application (to be exact: on root level they they are concealed by the bitmaps).
The reason is that my application uses the a different page template (No Tabs, Left and Right Sidebar, Theme 24 Cloudy).
The "Sample Tree" application (which has a reduced set of page templates) uses a template without sidebars (same Theme).
I was able to reproduce this error by switching the page template in the Oracle "Sample Tree" application to "Two level Tabs, Right Sidebar).
When I do so the tree line on root level disappear in the sample application also.
As I want to use a sidebar page template and want to use a navigation tree...
does anybody know a workaround for this behavior ?
I am using Chrome and Firefox on MacOS and the behavior ist the same in both browsers.
Thank very much ...
Telemat
Edited by: telemat on 03.08.2012 10:19

Hi,
I do not have access to your apex.oracle.com application to see what happens when the page template is changed.
It appears to render identical for various page templates in my local instance. I even tried with custom icons, 24-Cloudy. I am unable to spot the missing lines. Or, I do not see them rendered in any of the page templates ( corollary).
What appears to me on your apex.oracle.com application is that you are using icon that are not in the three options in the tree wizard (Blue/Classic/Default).
Moreover, your Tree does not have a single root that is displayed.
So, you either need to give access to your apex.oracle.com workspace for someone to try changing the template and see what is happening. Or, you need to describe how to locate the lines that find go missing.
Cheers.
PS : I am checking with FF 14 on Windows
Edited by: Prabodh on Aug 6, 2012 5:13 PM

Similar Messages

Possible Bug In Apex 4.0.2

Hi Everyone.
I would like to report what I think is a bug in Apex 4.0.2.
If you go to my workspace on apex.oracle.com:
Workspace = EEG
Username = [email protected]
Password = galaxy (all lowercase)
Run the application: 37796 - Elie_Various_Goodies [no credentials are required]
This app was imported from my 4.0.1 workspace at my job. On the page I created two Date Picker items, P1_BEGIN_DATE and P1_END_DATE. I set them up so that whenever a user selects a begin date, a dynamic action "MANAGE_DATES" fires and automatically sets P1_END_DATE to this selected begin date value. Now when a user goes to select an end date, the displayed calendar starts at the previously selected begin date rather than the default of "Today".
All of this worked fine on my office (4.0.1) workspace. However, after exporting this app and then importing onto apex.oracle.com, none of this functionality would work. Even worse, whenever I try to select a begin date or even an end date, the selected dates never make it into the date picker fields. Displaying the "Session" window shows these fields as empty.
It was only after I copied the two date picker fields and also re-created my dynamic action (P1_BEGIN_DATE2, P1_END_DATE2, MANAGE_DATES) did my functionality return.
This behavior is quite strange. I can only think this is some sort of bug attributed to the export/import process when exporting a 4.0.1 app into a 4.0.2 workspace. I am not sure if this bizarre behavior happens with non-date picker items. Nor am I sure if this beavior would be repeated if I export/import from 4.0.2 into the another 4.0.2 environment.
Another strange thing I noticed. If I change my date picker items to be "date picker (classic)" type items, the dynamic action does not work at all. This is true in both 4.0.2 and 4.0.1. I'm not sure if this a bug or not. It could be that the classic date picker is just not "javascript" enabled so to speak. If that is true, then it would have been nice if the docs would have warned us about this.
Has anyone else seen this behavior?
Thank you.
Elie

Hi Joel.
First let me thank you for the warning about allowing "everyone" access to my workspace.
You're correct, of course. Anyone could destroy anything within my workspace. I guess I was too trusting especially as I have seen many posts on the Forum where others have given access to their workspace so that responders can offer help. I really should be more discreet about this. Again, thank you. Needless to say, I have changed my password.
With respect to the possible bug, the MANAGE_DATES dynamic action is intended to be a submit page because that is the only way I can see to get BOTH the P1_END_DATE date picker item as well as the end date textual field to be assigned the selected P1_BEGIN_DATE. I tried to use a dynamic action in which javascript sets the value of the end date textual field to the selected P1_BEGIN_DATE value. This works without the need to submit the page. Unfortunately, this does not cause the P1_END_DATE date picker item to default to this value. Instead, the default remains at today's date. This is why I finally resorted to a dynamic action that submits the page whenever a new value is selected (that is, a "change" event) from the P1_BEGIN_DATE date picker item.
All of this works in my office 4.0.1 environment. However, I was puzzled when this fails under 4.0.2 on the hosted web site at apex.oracle.com. This is why I posted a "possible" bug in 4.0.2.
I hope this all makes sense.
One more thing, as already mentioned in my original post, this "defaulting a date picker" functionality does NOT work at all for the "classic" date picker items in both 4.0.1 nor in 4.0.2. I realize one can implement this functionality (I' guessing) my using, say, a "onChange" javascript call to submit the page. It's just funny that the "classic" date picker items are not acted upon by the dynamic action MANAGE_DATES that submits the page.
Thank you.
Elie

POSSIBLE BUG in APEX Version 3.2 "Copy Page"

Has anyone experienced an error in the *"Copy Lists of Values" step in the "Copy Page" application in 3.2*? I am experiencing a _"Report Error: ORA-06502: PL/SQL: numeric or value error: character string buffer too small"_ sometimes when I copy a page from one application to another. It appears to be page content related because I either always get it for a page or I never get it depending on what page I copy. When I get the error on a page copy, APEX hard codes the LOVs on the page into the list of values definitions instead of copying the appropriate Lists of Values in shared components and using them on the page. It is VERY irritating! Anyone know if this is a bug or if there is a way around it?
Dale

I was able to upload and install my application on apex.oracle.com and recreate the issue with the string length on the copy lists of values step in the page copy process. I have created an SR in Oracle Support and have provided them with the necessary information. Hopefully, they will be able to get a patch for the problem.
I was also able to recreate the problem with the change to the button template but, in the process, found that there is a simple work-around. When the page copy process gets to the copy templates step, it provides a list of the templates to be used. For some reason it does not choose the correct "Button for Javascript" template. Instead, it chooses the standard "Button" template. I was able to change it to use the correct template prior to clicking next. However, I think that the page copy process should be corrected to default the proper template in the first place.
Thanks Scott,
Dale

Possible bug in APEX 4.0.1: Websheet filter (interactive Reports) in German

Hi guys,
I just noticed that the filter criteria don't work when running the websheet application in German. It works in English though.
The interactive reports for the data grids and reports are affected.
Cheers,
~Diemar.
Edited by: Dietmar Aust on Sep 28, 2010 10:15 PM

Hi Dietmar,
i had the same problem today. All of the tables were missing. But i found a admin link with the possibility to install them. Please don´t ask me, where the link was (it´s more then 5 hours ago :-) )
HTH
Marco

Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
   (     "MICRO" VARCHAR2(4),
     "PRIM" VARCHAR2(4),
     "UNIT" NUMBER,
     "SEC_REF_1" NUMBER,
     "SECN_1" VARCHAR2(88),
     "SEC_REF_2" NUMBER,
     "SECN_2" VARCHAR2(88),
     "SEC_REF_3" NUMBER,
     "SECN_3" VARCHAR2(88),
     "SEC_REF_4" NUMBER,
     "SECN_4" VARCHAR2(88),
     "SEC_REF_5" NUMBER,
     "SECN_5" VARCHAR2(88),
     "SEC_REF_6" NUMBER,
     "SECN_6" VARCHAR2(88),
     "SEC_REF_7" NUMBER,
     "SECN_7" VARCHAR2(88),
     "SEC_REF_8" NUMBER,
     "SECN_8" VARCHAR2(88),
     "SEC_REF_9" NUMBER,
     "SECN_9" VARCHAR2(88),
     "SEC_REF_10" NUMBER,
     "SECN_10" VARCHAR2(88),
     "SEC_REF_11" NUMBER,
     "SECN_11" VARCHAR2(88),
     "SEC_REF_12" NUMBER,
     "SECN_12" VARCHAR2(88),
     "SEC_REF_13" NUMBER,
     "SECN_13" VARCHAR2(88),
     "SEC_REF_14" NUMBER,
     "SECN_14" VARCHAR2(88),
     "SEC_REF_15" NUMBER,
     "SECN_15" VARCHAR2(88),
     "SEC_REF_16" NUMBER,
     "SECN_16" VARCHAR2(88),
     "SEC_REF_17" NUMBER,
     "SECN_17" VARCHAR2(88),
     "SEC_REF_18" NUMBER,
     "SECN_18" VARCHAR2(88),
     "SEC_REF_19" NUMBER,
     "SECN_19" VARCHAR2(88),
     "SEC_REF_20" NUMBER,
     "SECN_20" VARCHAR2(88),
     "SEC_REF_21" NUMBER,
     "SECN_21" VARCHAR2(88),
     "SEC_REF_22" NUMBER,
     "SECN_22" VARCHAR2(88),
     "SEC_REF_23" NUMBER,
     "SECN_23" VARCHAR2(88),
     "SEC_REF_24" NUMBER,
     "SECN_24" VARCHAR2(88),
     "SEC_REF_25" NUMBER,
     "SECN_25" VARCHAR2(88),
     "SEC_REF_26" NUMBER,
     "SECN_26" VARCHAR2(88),
     "SEC_REF_27" NUMBER,
     "SECN_27" VARCHAR2(88),
     "SEC_REF_28" NUMBER,
     "SECN_28" VARCHAR2(88),
     "SEC_REF_29" NUMBER,
     "SECN_29" VARCHAR2(88),
     "SEC_REF_30" NUMBER,
     "SECN_30" VARCHAR2(88),
     "SEC_REF_31" NUMBER,
     "SECN_31" VARCHAR2(88),
     "SEC_REF_32" NUMBER,
     "SECN_32" VARCHAR2(88),
     "SEC_REF_33" NUMBER,
     "SECN_33" VARCHAR2(88),
     "SEC_REF_34" NUMBER,
     "SECN_34" VARCHAR2(88),
     "SEC_REF_35" NUMBER,
     "SECN_35" VARCHAR2(88),
     "SEC_REF_36" NUMBER,
     "SECN_36" VARCHAR2(88),
     "SEC_REF_37" NUMBER,
     "SECN_37" VARCHAR2(88),
     "SEC_REF_38" NUMBER,
     "SECN_38" VARCHAR2(88),
     "SEC_REF_39" NUMBER,
     "SECN_39" VARCHAR2(88),
     "SEC_REF_40" NUMBER,
     "SECN_40" VARCHAR2(88),
     "SEC_REF_41" NUMBER,
     "SECN_41" VARCHAR2(88),
     "SEC_REF_42" NUMBER,
     "SECN_42" VARCHAR2(88),
     "SEC_REF_43" NUMBER,
     "SECN_43" VARCHAR2(88),
     "SEC_REF_44" NUMBER,
     "SECN_44" VARCHAR2(88),
     "SEC_REF_45" NUMBER,
     "SECN_45" VARCHAR2(88),
     "SEC_REF_46" NUMBER,
     "SECN_46" VARCHAR2(88),
     "SEC_REF_47" NUMBER,
     "SECN_47" VARCHAR2(88),
     "SEC_REF_48" NUMBER,
     "SECN_48" VARCHAR2(88),
     "SEC_REF_49" NUMBER,
     "SECN_49" VARCHAR2(88),
     "SEC_REF_50" NUMBER,
     "SECN_50" VARCHAR2(88),
     "SEC_REF_51" NUMBER,
     "SECN_51" VARCHAR2(88),
     "SEC_REF_52" NUMBER,
     "SECN_52" VARCHAR2(88),
     "SEC_REF_53" NUMBER,
     "SECN_53" VARCHAR2(88),
     "SEC_REF_54" NUMBER,
     "SECN_54" VARCHAR2(88),
     "SEC_REF_55" NUMBER,
     "SECN_55" VARCHAR2(88),
     "SEC_REF_56" NUMBER,
     "SECN_56" VARCHAR2(88),
     "SEC_REF_57" NUMBER,
     "SECN_57" VARCHAR2(88),
     "SEC_REF_58" NUMBER,
     "SECN_58" VARCHAR2(88),
     "SEC_REF_59" NUMBER,
     "SECN_59" VARCHAR2(88),
     "SEC_REF_60" NUMBER,
     "SECN_60" VARCHAR2(88),
     "SEC_REF_61" NUMBER,
     "SECN_61" VARCHAR2(88),
     "SEC_REF_62" NUMBER,
     "SECN_62" VARCHAR2(88),
     "SEC_REF_63" NUMBER,
     "SECN_63" VARCHAR2(88),
     "SEC_REF_64" NUMBER,
     "SECN_64" VARCHAR2(88),
     "SEC_REF_65" NUMBER,
     "SECN_65" VARCHAR2(88),
     "SEC_REF_66" NUMBER,
     "SECN_66" VARCHAR2(88),
     "SEC_REF_67" NUMBER,
     "SECN_67" VARCHAR2(88),
     "SEC_REF_68" NUMBER,
     "SECN_68" VARCHAR2(88),
     "SEC_REF_69" NUMBER,
     "SECN_69" VARCHAR2(88),
     "SEC_REF_70" NUMBER,
     "SECN_70" VARCHAR2(88),
     "SEC_REF_71" NUMBER,
     "SECN_71" VARCHAR2(88),
     "SEC_REF_72" NUMBER,
     "SECN_72" VARCHAR2(88),
     "SEC_REF_73" NUMBER,
     "SECN_73" VARCHAR2(88),
     "SEC_REF_74" NUMBER,
     "SECN_74" VARCHAR2(88),
     "SEC_REF_75" NUMBER,
     "SECN_75" VARCHAR2(88),
     "SEC_REF_76" NUMBER,
     "SECN_76" VARCHAR2(88),
     "SEC_REF_77" NUMBER,
     "SECN_77" VARCHAR2(88),
     "SEC_REF_78" NUMBER,
     "SECN_78" VARCHAR2(88),
     "SEC_REF_79" NUMBER,
     "SECN_79" VARCHAR2(88),
     "SEC_REF_80" NUMBER,
     "SECN_80" VARCHAR2(88),
     "SEC_REF_81" NUMBER,
     "SECN_81" VARCHAR2(88),
     "SEC_REF_82" NUMBER,
     "SECN_82" VARCHAR2(88),
     "SEC_REF_83" NUMBER,
     "SECN_83" VARCHAR2(88),
     "SEC_REF_84" NUMBER,
     "SECN_84" VARCHAR2(88),
     "SEC_REF_85" NUMBER,
     "SECN_85" VARCHAR2(88),
     "SEC_REF_86" NUMBER,
     "SECN_86" VARCHAR2(88),
     "SEC_REF_87" NUMBER,
     "SECN_87" VARCHAR2(88),
     "SEC_REF_88" NUMBER,
     "SECN_88" VARCHAR2(88),
     "SEC_REF_89" NUMBER,
     "SECN_89" VARCHAR2(88),
     "SEC_REF_90" NUMBER,
     "SECN_90" VARCHAR2(88),
     "SEC_REF_91" NUMBER,
     "SECN_91" VARCHAR2(88),
     "SEC_REF_92" NUMBER,
     "SECN_92" VARCHAR2(88),
     "SEC_REF_93" NUMBER,
     "SECN_93" VARCHAR2(88),
     "SEC_REF_94" NUMBER,
     "SECN_94" VARCHAR2(88),
     "SEC_REF_95" NUMBER,
     "SECN_95" VARCHAR2(88),
     "SEC_REF_96" NUMBER,
     "SECN_96" VARCHAR2(88),
     "SEC_REF_97" NUMBER,
     "SECN_97" VARCHAR2(88),
     "SEC_REF_98" NUMBER,
     "SECN_98" VARCHAR2(88),
     "SEC_REF_99" NUMBER,
     "SECN_99" VARCHAR2(88),
     "SEC_REF_100" NUMBER,
     "SECN_100" VARCHAR2(88),
     "SEC_REF_101" NUMBER,
     "SECN_101" VARCHAR2(88),
     "SEC_REF_102" NUMBER,
     "SECN_102" VARCHAR2(88),
     "SEC_REF_103" NUMBER,
     "SECN_103" VARCHAR2(88),
     "SEC_REF_104" NUMBER,
     "SECN_104" VARCHAR2(88),
     "SEC_REF_105" NUMBER,
     "SECN_105" VARCHAR2(88),
     "SEC_REF_106" NUMBER,
     "SECN_106" VARCHAR2(88),
     "SEC_REF_107" NUMBER,
     "SECN_107" VARCHAR2(88),
     "SEC_REF_108" NUMBER,
     "SECN_108" VARCHAR2(88),
     "SEC_REF_109" NUMBER,
     "SECN_109" VARCHAR2(88),
     "SEC_REF_110" NUMBER,
     "SECN_110" VARCHAR2(88),
     "SEC_REF_111" NUMBER,
     "SECN_111" VARCHAR2(88),
     "SEC_REF_112" NUMBER,
     "SECN_112" VARCHAR2(88),
     "SEC_REF_113" NUMBER,
     "SECN_113" VARCHAR2(88),
     "SEC_REF_114" NUMBER,
     "SECN_114" VARCHAR2(88),
     "SEC_REF_115" NUMBER,
     "SECN_115" VARCHAR2(88),
     "SEC_REF_116" NUMBER,
     "SECN_116" VARCHAR2(88),
     "SEC_REF_117" NUMBER,
     "SECN_117" VARCHAR2(88),
     "SEC_REF_118" NUMBER,
     "SECN_118" VARCHAR2(88),
     "SEC_REF_119" NUMBER,
     "SECN_119" VARCHAR2(88),
     "SEC_REF_120" NUMBER,
     "SECN_120" VARCHAR2(88),
     "SEC_REF_121" NUMBER,
     "SECN_121" VARCHAR2(88),
     "SEC_REF_122" NUMBER,
     "SECN_122" VARCHAR2(88),
     "SEC_REF_123" NUMBER,
     "SECN_123" VARCHAR2(88),
     "SEC_REF_124" NUMBER,
     "SECN_124" VARCHAR2(88),
     "SEC_REF_125" NUMBER,
     "SECN_125" VARCHAR2(88),
     "SEC_REF_126" NUMBER,
     "SECN_126" VARCHAR2(88),
     "SEC_REF_127" NUMBER,
     "SECN_127" VARCHAR2(88),
     "SEC_REF_128" NUMBER,
     "SECN_128" VARCHAR2(88),
     "SEC_REF_129" NUMBER,
     "SECN_129" VARCHAR2(88),
     "SEC_REF_130" NUMBER,
     "SECN_130" VARCHAR2(88),
     "SEC_REF_131" NUMBER,
     "SECN_131" VARCHAR2(88),
     "SEC_REF_132" NUMBER,
     "SECN_132" VARCHAR2(88),
     "SEC_REF_133" NUMBER,
     "SECN_133" VARCHAR2(88),
     "SEC_REF_134" NUMBER,
     "SECN_134" VARCHAR2(88),
     "SEC_REF_135" NUMBER,
     "SECN_135" VARCHAR2(88),
     "SEC_REF_136" NUMBER,
     "SECN_136" VARCHAR2(88),
     "SEC_REF_137" NUMBER,
     "SECN_137" VARCHAR2(88),
     "SEC_REF_138" NUMBER,
     "SECN_138" VARCHAR2(88),
     "SEC_REF_139" NUMBER,
     "SECN_139" VARCHAR2(88),
     "SEC_REF_140" NUMBER,
     "SECN_140" VARCHAR2(88),
     "SEC_REF_141" NUMBER,
     "SECN_141" VARCHAR2(88),
     "SEC_REF_142" NUMBER,
     "SECN_142" VARCHAR2(88),
     "SEC_REF_143" NUMBER,
     "SECN_143" VARCHAR2(88),
     "SEC_REF_144" NUMBER,
     "SECN_144" VARCHAR2(88),
     "SEC_REF_145" NUMBER,
     "SECN_145" VARCHAR2(88),
     "SEC_REF_146" NUMBER,
     "SECN_146" VARCHAR2(88),
     "SEC_REF_147" NUMBER,
     "SECN_147" VARCHAR2(88),
     "SEC_REF_148" NUMBER,
     "SECN_148" VARCHAR2(88),
     "SEC_REF_149" NUMBER,
     "SECN_149" VARCHAR2(88),
     "SEC_REF_150" NUMBER,
     "SECN_150" VARCHAR2(88),
     "SEC_REF_151" NUMBER,
     "SECN_151" VARCHAR2(88),
     "SEC_REF_152" NUMBER,
     "SECN_152" VARCHAR2(88),
     "SEC_REF_153" NUMBER,
     "SECN_153" VARCHAR2(88),
     "SEC_REF_154" NUMBER,
     "SECN_154" VARCHAR2(88),
     "SEC_REF_155" NUMBER,
     "SECN_155" VARCHAR2(88),
     "SEC_REF_156" NUMBER,
     "SECN_156" VARCHAR2(88),
     "SEC_REF_157" NUMBER,
     "SECN_157" VARCHAR2(88),
     "SEC_REF_158" NUMBER,
     "SECN_158" VARCHAR2(88),
     "SEC_REF_159" NUMBER,
     "SECN_159" VARCHAR2(88),
     "SEC_REF_160" NUMBER,
     "SECN_160" VARCHAR2(88),
     "SEC_REF_161" NUMBER,
     "SECN_161" VARCHAR2(88),
     "SEC_REF_162" NUMBER,
     "SECN_162" VARCHAR2(88),
     "SEC_REF_163" NUMBER,
     "SECN_163" VARCHAR2(88),
     "SEC_REF_164" NUMBER,
     "SECN_164" VARCHAR2(88),
     "SEC_REF_165" NUMBER,
     "SECN_165" VARCHAR2(88),
     "SEC_REF_166" NUMBER,
     "SECN_166" VARCHAR2(88),
     "SEC_REF_167" NUMBER,
     "SECN_167" VARCHAR2(88),
     "SEC_REF_168" NUMBER,
     "SECN_168" VARCHAR2(88),
     "SEC_REF_169" NUMBER,
     "SECN_169" VARCHAR2(88),
     "SEC_REF_170" NUMBER,
     "SECN_170" VARCHAR2(88),
     "SEC_REF_171" NUMBER,
     "SECN_171" VARCHAR2(88),
     "SEC_REF_172" NUMBER,
     "SECN_172" VARCHAR2(88),
     "SEC_REF_173" NUMBER,
     "SECN_173" VARCHAR2(88),
     "SEC_REF_174" NUMBER,
     "SECN_174" VARCHAR2(88),
     "SEC_REF_175" NUMBER,
     "SECN_175" VARCHAR2(88),
     "SEC_REF_176" NUMBER,
     "SECN_176" VARCHAR2(88),
     "SEC_REF_177" NUMBER,
     "SECN_177" VARCHAR2(88),
     "SEC_REF_178" NUMBER,
     "SECN_178" VARCHAR2(88),
     "SEC_REF_179" NUMBER,
     "SECN_179" VARCHAR2(88),
     "SEC_REF_180" NUMBER,
     "SECN_180" VARCHAR2(88),
     "SEC_REF_181" NUMBER,
     "SECN_181" VARCHAR2(88),
     "SEC_REF_182" NUMBER,
     "SECN_182" VARCHAR2(88),
     "SEC_REF_183" NUMBER,
     "SECN_183" VARCHAR2(88),
     "SEC_REF_184" NUMBER,
     "SECN_184" VARCHAR2(88),
     "SEC_REF_185" NUMBER,
     "SECN_185" VARCHAR2(88),
     "SEC_REF_186" NUMBER,
     "SECN_186" VARCHAR2(88),
     "SEC_REF_187" NUMBER,
     "SECN_187" VARCHAR2(88),
     "SEC_REF_188" NUMBER,
     "SECN_188" VARCHAR2(88),
     "SEC_REF_189" NUMBER,
     "SECN_189" VARCHAR2(88),
     "SEC_REF_190" NUMBER,
     "SECN_190" VARCHAR2(88),
     "SEC_REF_191" NUMBER,
     "SECN_191" VARCHAR2(88),
     "SEC_REF_192" NUMBER,
     "SECN_192" VARCHAR2(88),
     "SEC_REF_193" NUMBER,
     "SECN_193" VARCHAR2(88),
     "SEC_REF_194" NUMBER,
     "SECN_194" VARCHAR2(88),
     "SEC_REF_195" NUMBER,
     "SECN_195" VARCHAR2(88),
     "SEC_REF_196" NUMBER,
     "SECN_196" VARCHAR2(88),
     "SEC_REF_197" NUMBER,
     "SECN_197" VARCHAR2(88),
     "SEC_REF_198" NUMBER,
     "SECN_198" VARCHAR2(88),
     "SEC_REF_199" NUMBER,
     "SECN_199" VARCHAR2(88),
     "SEC_REF_200" NUMBER,
     "SECN_200" VARCHAR2(88),
     "SEC_REF_201" NUMBER,
     "SECN_201" VARCHAR2(88),
     "SEC_REF_202" NUMBER,
     "SECN_202" VARCHAR2(88),
     "SEC_REF_203" NUMBER,
     "SECN_203" VARCHAR2(88),
     "SEC_REF_204" NUMBER,
     "SECN_204" VARCHAR2(88),
     "SEC_REF_205" NUMBER,
     "SECN_205" VARCHAR2(88),
     "SEC_REF_206" NUMBER,
     "SECN_206" VARCHAR2(88),
     "SEC_REF_207" NUMBER,
     "SECN_207" VARCHAR2(88),
     "SEC_REF_208" NUMBER,
     "SECN_208" VARCHAR2(88)
   );Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PM

So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil?

Is it possible to stop APEX using a cached query?

I was hoping that the issue where report regions sometimes show the error: "ORA-06502: PL/SQL: numeric or value error: NULL index table key value" would be fixed in 3.1.1 however it seems not to have been (We have had it several times now). The workaround seems to be to change the query slightly such as selecting NULL as an additional column and then hiding that column.
This obviously only works AFTER the issue has occured, ie, after we have received a complaint from someone!
Is it possible to stop APEX using the cached version of some queries altogether? The ones we are calling are quite simple and so will not give that much overhead.
Thanks.

I've actually found several threads on this from the past:
ORA-06502: PL/SQL: numeric or value error: NULL index table key value
http://kr.forums.oracle.com/forums/thread.jspa?threadID=644172&tstart=120 (This thread states the problem has been fixed however it would appear either it hasn't or there is a similar bug elsewhere.)

Scrollbar in a classic Apex 4.1 tree

In Apex 4.1 it looks like it is not possible for a new Apex 4.1 tree to adjust its template HTML settings.
It can't be found in the shared components for instance.
To be able to change some of the html style settings you can add a javascript in the "Execute when Page Loads" javascript settings of the page where the tree is located.
Here is an example of adding a scrollbar to an Apex 4.1 tree:
// Get div element of the tree. You can use firebug to determine the id of the tree
d = document.getElementById('tree160968347950446047');
// Show scrollbars when the tree data extends the maximum height
// If you only need a vertical bar you can use 'overflowY' instead
d.style.overflow="auto";
// Set the width of the tree
d.style.width="500px";
// Set maximum height of the tree
d.style.maxHeight="460px";
// Microsoft Internet Explorer ignores the maxHeight style. So use height instead.
// To avoid that the other browsers use this height style, give the height 1 px more than the maxHeight
d.style.height="461px";
Regards,
Mathieu

Hi Mathieu,
Any chance that you might know the code to move the selected tree node to the top of the scrollbar region? I've done it previously as per
APEX Tree. Keep focus on expanded leaf node.
but don't know where to put all this code now that we do not have access to the tree templates in V4+
regards
Paul P

How to auto refresh a tree region

Is possible to automaticaly refresh a tree region?

Anyone can help me with this?
Edited by: macwadu on 4/Ago/2011 3:10

On-demand process in page processing - possible bug?

Hi
Came across a possible bug today, certainly not a big one and unlike to affect many people but...
1. Create an on-demand application process
2. Create an on-demand page process that calls the application process
3. Delete the application process.
Now at this point, the page process is still available for editing/deleting etc.
4. Copy the application.
In the new version of the application, the page process shows as plain text in the application builder with no link to edit or delete it and when the page is run, it predictably fails at the processing point of the page process when it tries to find the application process (the id from wwv_flow_processing is shown in the error for the old application process).
The only way to get rid of the page process is to select 'Edit All' and then select and delete it - then everything is hunky dory again.
A minor issue I know, but maybe someone will have the same issue one day and stumble across this thread :)
Cheers
Ben

At the moment I cannot say if your link can help. Right now the call of the On demand Process looks like this:
Inside annonymous PL/SQL Region:
<script type="text/javascript">
get = new htmldb_Get(null,'||:APP_ID||'.,'APPLICATION_PROCESS=F_REPORT_NAME',0);
gReturn = get.get();
document.write(gReturn);
</script>

Tree Region Example

Hi,
I'm using my apex.oracle.com workspace. I'm trying to create a tree region using the emp table. I'm using the typical wizard but when i run the page the tree is not displayed.
This is the query built by apex with the wizard.
select case when connect_by_isleaf = 1 then 0
when level = 1 then 1
else -1
end as status,
level,
"ENAME" as title,
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"
http://apex.oracle.com/pls/apex/f?p=41771:3:8143710593092:::::

Run page : runs fine - no errors.
Execute SQL in workshop:
No data found.Okay. So obviously data related.
select * from emp
16 rows returnedGreat.
Connect by start with clause:
start with "MGR" is nullOops. No records where "MGR" is null. No tree!

How many items are possible in page APEX 3.2

Hi All,
I have created around 95 page items,8 different region , 10 buttons and i have used collections in page processing
While processing the page by using Select with LOV getting error http://3264-ch-dbs:8080/apex/wwv_flow.accept
I have created 15 extra page item due whih count increases from 80 to 95 .once I have created this I tried processing the page by select list with submit . I am getting above mentioned error
how many items are possible in page APEX 3.2 , is there limitation ?
Any sugeestion is welcomed
Thanks and Regards
Sachin

Hello Sachin,
>> how many items are possible in page APEX 3.2 , is there limitation ?
You can render up to 100 APEX item on the page, and that includes hidden items. You can define more than 100 items and use conditions to determine which items will be rendered. (Buttons and other components you mentioned are not included in the 100 count).
Regards,
Arie.
&diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
&diams; Forthcoming book about APEX: Oracle Application Express 3.2 – The Essentials and More

Interesting problem with Tree region...

HI
I have a tree region which I am using to show tasks in a task management / change control app. All working fine until I decided it would be good to have a select list at the top which allows me to see either all or just incomplete tasks...
I set up a list selection item (P9_TASK_STATUS) with the following LOV:
STATIC:All;101,Incomplete;100
Then I modified the tree code to include ' AND pcent_complete < :P9_TASK_STATUS ' in the where clause (code below). Now, when I choose All from the drop down I see all nodes. When I choose Incomplete I see nothing... an empty tree! I have checked the value in P9_TASK_STATUS and it is as per the LOV...
I tested the code by changing it to hard numbers instead of the item - and it works fine when I use ' < 101' but returns nothing when I use '< 100'. Have also tried changing the LOV to 100 & 90 then putting a '<=' in the where clause.
Yes, there are many tasks with values less than 100!!
Any ideas?
Thanks in advance
Steve
select case when connect_by_isleaf = 1 then 0
when level = 1 then 1
else -1
end as status,
level,
"TASK_NAME" as title,
null as icon,
"TASK_ID" as value,
"DETAIL" as tooltip,
'f?p=&APP_ID.:9:&APP_SESSION.::::P9_TASK_ID_1,P9_TREE_NODE:'||"TASK_ID" || ',' || "TASK_ID" as link
from "#OWNER#"."TM020_TASKS"
WHERE project_id = :F102_PROJID and pcent_complete < :P9_TASK_STATUS
start with "TASK_LEVEL" = 1
connect by prior "TASK_ID" = PARENT
order siblings by dte_sched, priority
Edited by: Steve In Dorset, UK on Jan 13, 2011 9:46 AM

Hi
Interesting point ab out the where clause but that works fine with the single condition to filter by project ID. I've also noticed that the problem only occurs once there are tasks which have been marked as 100% complete! WHen there are no complete tasks the code runs OK. could be an excuse to never finish a task...
COde to create table & data below
Thanks
Steve
-- DDL for Table TM020_TASKS
CREATE TABLE "TM020_TASKS"
(     "TASK_ID" NUMBER(*,0),
     "PROJECT_ID" NUMBER(*,0),
     "TASK_NAME" VARCHAR2(100),
     "PARENT" NUMBER(*,0) DEFAULT 0,
     "REQUESTOR" VARCHAR2(25 CHAR),
     "DETAIL" CLOB,
     "DTE_CREATED" DATE DEFAULT sysdate,
     "DTE_STARTED" DATE,
     "DTE_DUE" DATE,
     "DTE_LIVE" DATE,
     "PRIORITY" NUMBER(*,0) DEFAULT 0,
     "PCENT_COMPLETE" NUMBER(*,0) DEFAULT 0,
     "WORK_SEQ" NUMBER(*,0) DEFAULT 0,
     "TASK_LEVEL" NUMBER(*,0) DEFAULT 1,
     "DEV_NOTES" CLOB,
     "DTE_TEST" DATE,
     "DB_OBJ" VARCHAR2(100),
     "APP_OBJ" VARCHAR2(100),
     "DTE_SCHED" DATE,
     "OWNER" NUMBER(*,0) DEFAULT 0
REM INSERTING into TM020_TASKS
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (48,13,'Calendar Reports',43,'Anne',to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,3,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (39,15,'Bugs',0,'Everyone!',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,1,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (40,15,'Email to Postmaster',39,'Caroline',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,to_date('14-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,0,null,2,null,null,null,to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (41,13,'Create table for tree',19,null,to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('10-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('10-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,1,100,null,3,to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),'icdb501_admintree',null,to_date('10-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (42,13,'Bugs',0,null,to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,1,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (43,13,'Change Requests',0,null,to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,1,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (44,13,'Download CSV Change',42,'Anne',to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,2,0,null,2,null,null,null,to_date('16-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (45,13,'Reports',0,null,to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,1,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (46,13,'% Pats screened',45,'Anne',to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,1,0,null,2,null,null,null,to_date('17-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (47,13,'Patient Status',43,'Anne',to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,1,0,null,2,null,null,null,to_date('17-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (49,13,'Positive TCIs',48,'Anne',to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,2,0,null,4,null,null,null,to_date('18-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (14,13,'Make Admin more friendly',0,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,to_date('14-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,40,0,1,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (16,15,'Change Requests',0,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,0,1,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (18,17,'Create project docs structure',0,'System',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,0,1,null,null,null,null,0);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (19,13,'Set up IC Tree region',14,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('07-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('18-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,50,null,2,to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,to_date('07-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (20,13,'Plan IC tree nodes',19,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('09-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('09-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,100,null,3,null,null,null,to_date('09-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (21,13,'Create IC node pages',19,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('07-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,100,null,3,null,null,null,to_date('09-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (22,13,'Help & Support',0,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,to_date('21-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,0,null,1,null,null,null,to_date('17-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (23,13,'On-Line Help',22,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,to_date('21-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (24,13,'Written manuals',22,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,to_date('21-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (25,13,'Helpdesk documentation',22,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,to_date('21-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (26,15,'Split large fields',16,'Steve',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,2,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (27,15,'Ward activation',16,'Caroline',to_date('11-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,2,0,null,2,null,null,'listmanager.asp',null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (28,13,'Set up Micro tree region',14,'Steve',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (29,13,'Plan Micro tree nodes',28,'Steve',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,3,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (30,13,'Create micro node pages',28,'Steve',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,3,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (32,31,'Clinic Letters',0,'Caroline',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,0,1,null,null,null,null,0);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (33,31,'Remove interprovide mail',32,'Caroline',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,1,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (34,31,'PAS',0,null,to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,1,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (35,31,'get TRUD',34,'Caroline',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,2,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (36,31,'Enable samba for trud',34,'Caroline',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,0,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (37,31,'HL7 email',34,'Caroline',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,null,null,1,0,null,2,null,null,null,null,1);
Insert into TM020_TASKS (TASK_ID,PROJECT_ID,TASK_NAME,PARENT,REQUESTOR,DTE_CREATED,DTE_STARTED,DTE_DUE,DTE_LIVE,PRIORITY,PCENT_COMPLETE,WORK_SEQ,TASK_LEVEL,DTE_TEST,DB_OBJ,APP_OBJ,DTE_SCHED,OWNER) values (38,13,'Create icdb530_pk_trg',21,'Steve',to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),null,2,100,null,4,to_date('13-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),'icdb530_pk_trg',null,to_date('12-JAN-11 00.00.00','DD-MON-RR HH24.MI.SS'),1);

How to add vertical scrollbar to a tree region

Hi,
I have a page containing two regions. The first is a tree region displayed on the left hand side of the page. The second is form region displayed to the right of the tree, showing details relating to the selected node from the tree.
How can I add a vertical scrollbar to the tree, so that I can I browse all nodes in the tree without affecting the position of the form? Currently, if my tree extends beyond the height of the page I have to use the page vertical scrollbar to view the bottom of the tree. This obviously means that the form is no longer in view.
Thanks
Andrew.

Hi Andrew,
You can't add a scrollbar directly to the region's contents, but you can wrap the contents within a DIV tag.
In the Region Header add in:
<DIV style="height:500px; overflow:auto">
In the Region Footer add in:
</DIV>
Obviously, change the height value to suit your needs.
Regards
Andy

Is it possible to change the color of the regions in GB 11?

Is it possible to change the color of the regions in GB 11?

Gourmet Pizza wrote:
Is it possible to change the color of the regions in GB 11?
only an imported orange region (to purple):
http://www.bulletsandbones.com/GB/GBFAQ.html#orangetopurple
(Let the page FULLY load. The link to your answer is at the top of your screen)

Open Cursor Issue because of file browse Item - Is this a Bug in APEX 3.2

Hi All,
I am using file browse Item to upload file into the database at two places in my application, but it seems whenever I am submitting those two pages, with file path or without file path, its opening an cursor which remains open after that, because of this open cursor count in the application is getting exceeding every time.
For testing this I have made an dummy page containing just file browse item and submit button, and still it is increasing the open cursor count.
Is this a bug in Apex file browse item or there is some other way to handle this.
Please kindly help me in the above issue as this is affecting the production application.
Thanks & Regards
Sanjay
Edited by: user11204334 on Dec 5, 2010 9:57 PM
Edited by: user11204334 on Dec 5, 2010 9:58 PM

Hi,
One observation, Apex is switching the Session ID after one got killed ? I was working on Apex page with browse Item to test open cursor count,
after killing the SID (227) on which the open cursor count was getting increase, it APEX automatically switches to new SID(149) for that session.
Now the problem is even if I have two SID's and one hits the maximum open cursor count, It is not switching to other SID instead the whole application becomes unavailable.
STATNAME SID VALUE USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 74 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 227 325 APEX_PUBLIC_USER Killed
opened cursors current 244 15 APEX_PUBLIC_USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 76 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 244 15 APEX_PUBLIC_USER
Please kindly help in this.
Thanks in Advance
Thanks & Regards
Sanjay
Edited by: user11204334 on Dec 8, 2010 1:02 AM

Possible Bug in APEX 4.1 Tree Region

Similar Messages

Maybe you are looking for