Read only item populated by dynamic LOV

Since I'm using artificial keys in most of my table FKs, I need to use a lot of LOVs to provide the user with discernible data.
Many of the columns I use an LOV for I need to be read only items. However, whenever I use a dynamic LOV, I do not see how to make it read only. It sets the value of the item to [].
I know this can be accomplished in some cases with a join in the underlying query. However, many of the pages where I need to make this change are not based on a query.
Is there a way to make an item populated by an LOV read only while still retaining the value?
Thanks for your help!
-Reid

I'm using apex 3.2.1. Your testing and replies have helped me realize that the problem is that the column indeed did not have a value. When I had the item "display as" set to "select list" the LOV was also setup for allow NULL=NO. Thus, it was showing some value in the LOV in that item. But, when I switched to the "display as text" and set the always read only, then it gave the double brackets []. When I changed the allow NULL=YES, it worked fine and gave me a blank value.
Thanks again!
-Reid

Similar Messages

Defaulting Values and Read-Only Items?

Hi All,
Brand new to APEX and trying to think of ways to get a few things working for me hoping you might have some suggestions.
1. Want to have a few items default upon the creation of a record.
- Created Date - have a column/page item that I would like to default/auto populate with the current date
- Create by - would like to have column/page item default with the login id of the user
2. Dynamically make page/items read-only.
- Once a record is created I would like to ensure that the only person able to edit the record would be the creator. I assume I can use the Read Only feature at the item level but am unsure of the syntax to use to make the item read-only for only the user who created/or is creating the record. Since I would like to be defaulting the "Create by" (see question 1) column to the login id of the user this should be plausible just not sure of the syntax to reference the current user id.
3. Passing a value to to bind variable.
- I have build a basic page with an Interactive Report and have made one of the columns in the Interactive report 'linkable' which launches a BI Publisher report by calling a Report Query. Currently in my report query I have hard coded a value in the SQL statements where clause to prove the theory works what I am struggling with is a declarative way to pass the value that I am clicking to a bind variable in my SQL statements where clause in the query.
Thanks in advance for any suggestions and appreciate your patience with an APEX newbie .. about 2 days old at this juncture. The more specific you can be on what to do and where to go is greatly appreciated.
For those interested in have greater control with your report layout BI Publisher looks to be a great options. I was able to getting by reviewing [how to document:|http://www.oracle.com/technology/products/database/application_express/howtos/howto_master_detail_pdf.html] on OTN. My challenge some in the fact that rather then simply being on the exact row that I want reported on I would like to simply click on a link in a list and pass that value as the bind variable.
JES

Hi -
"1. Want to have a few items default upon the creation of a record."
This is typically done in a trigger at the db level.
CREATE OR REPLACE TRIGGER mytrigger
BEFORE INSERT OR UPDATE
ON mytable
REFERENCING NEW AS new OLD AS old
FOR EACH ROW
BEGIN
if (:new.CREATED_DATE is null)
    then
      :new.CREATED_DATE := sysdate;
    end if;
if (:new.CREATED_USER is null)
    then
      :new.CREATED_USER := nvl(v('APP_USER'),user);
    end if;
:new.UPDATED_DATE := sysdate;
:new.UPDATED_USER := nvl(v('APP_USER'),user);
END CREATE OR REPLACE TRIGGER mytrigger;"2. Dynamically make page/items read-only."
See 'APP_USER' in the Apex docs...
"3. Passing a value to to bind variable."
This is done in the report configuration in the Apex UI...
Session State Include application and session information.
You might want to consider reviewing some of the Apex docs and tutorials, I recommend this:
[http://download.oracle.com/docs/cd/E14373_01/appdev.32/e13367/toc.htm]
Good luck.

Are 'read only' items causing my automatic row processing to fail?

I have a form that uses automatic row processing to update my table.
I recently had to add a check to lock down the fields using the read only condition where a record has been 'approved'. So, I turned off all of the fields and hid the update button.
Now they want me to check to see if the user is a manager, and if so, allow them to see the update button, and make a single field on the form modifiable.
I have the user identified as a manager, and can make the field accept the change (a yes/no combo box). Yet when they click the update button, the form just sits there. A branch is supposed to fire on hitting that button, taking them back to the previous report, but it doesn't happen. The source of the combo box in question uses a column on the table, and works fine when the form has all of the fields showing for modification.
I had some validations that I finally set to never fire, thinking that they were failing and just not giving the error messages. I know a bad sql or pl/sql atatement in a validation will cause the form to just keep sitting there doing nothing, and thought it might help.
Several of the various fields are combo boxes, several are text boxes.
I'm stumped.
Shall I keep the regular update button hidden whether it is a manager or not (because it has been 'approved'), and enable a new button that fires off a process to update the one field that the manager may want to change? Does making a field 'read only' always have a detrimental effect on the auto processes I've been counting on? Is that if fact what is happening now?
Thanks in advance for any advice or comments on this.
Clayton

Hi, Scott.
My version is 3.0.0.00.20
I have received info to set up the application, though I have not activated it as yet. I'm reluctant to try to load up the various tables to make it work. It could be done.
My workaround is to that the user (a manager) fires off to another form to show an individual record, and ask if he/she really wants to make this change. On submit, they will be taken back to the original locked down form, and I will update the single field in that process of returning them. This will actually be a plus, in that I expect to show them all of the 'duplicate' entries for that item, and show them that by 'activating' this particular item, they will 'deactivate' the one duplicate that is currently active. Or, if they are deactivating the sole item that is active, that there will in fact be no active items in the system. Convoluted as heck, but they swear this is how they've been doing business with their briefcases and file cabinets of Excel files. I'm surprise they even float at this point (these are ships we're talking about).
This all may be due to the form originally having a next/previous/count process once arrived at my clicking on the edit button of the report of items. All of that has been hidden away, and though the fields exist of the form, they are not used. They only see the current item that they clicked on from the report.
I read up a little on session state, as well as posts with the debug error I was getting. I'm still not on board with the whole issue of 'state'. Items stay as they are until they're changed, no? I suppose that sounds simplistic.
One of the things that caught my eye was several combo box lists that on read only mode, showed [] square brackets. Which, in some cases is okay.
What I'll try to do is set up a public application - for future use if nothing else. I'm going to be working on this for awhile. I have more than a bit of work to do to cleanse the data as well as get rid of the single sign on requirement (I'll assume that I should have to do this) in order to share the app.
I know you're expecting me to have this up and running for you to look at, but I'm under the gun. And they actually like my workaround.
I'll keep everybody informed, one way or another.
Clayton

Can I suppress HTML escaping in a read-only item?

I have an item that is displayed as read-only. The item contains HTML markup. HTML DB seems to automatically escape special characters in the item value.
Is there a way to suppress this?
For example, I have a text input item with the value:
<b>Hello</b>
(that is, it contains the bold elements which I want to output as is).
HTML DB seems to be escaping the item value so I see the bold elements in the browser and what I see in the page source is: &lt;b&gt;Hello&lt;/b&gt;
There doesn't seem to be "escape special characters" / "don't escape special characters" options for read-only mode like there is for "Display As Text" items. Can anyone suggest a workaround?
Thanks,
Eric

Eric - Text input items are escaped on output whether they are read-only or not. But to answer your question generally, APEX does not emit input items of any type to the browser without escaping them unless there is a guarantee that they have been escaped on input, e.g., when passed in through the URL, or that they acquired their value from within the application. These guarantees apply only to non-POSTable item types such as Display As Text (does not save state) items and a couple others. So in short, we observe the rule (which should be observed by app developers) that it is never safe (from an XSS-protection standpoint) to emit a POSTable item without escaping it first.
In your case, can you define a safe item type (Display as Text, does not save state) and set its source to the markup-containing item that you are now displaying as read-only? If so, you can conditionally display only the safe one and hide the other.
Scott

Session state protection and read-only items

I have a requirement to create a report + form for a database table. In the form, there is mandatory database column that needs to be displayed but it should be read-only and its value derived using values entered elsewhere on the screen.
It tried Display Only, Read Only and Disabled but they either fall foul of session state protection violation or ORA-01400: cannot insert NULL. The best method that I've found was to add readonly="readonly" the item element, but this causes the input item to lose its APEX classes and I'd prefer a declarative solution anyway.
Anyone know the best approach?
I've created a DEMO - http://apex.oracle.com/pls/apex/f?p=READONLY - which demonstrates the 4 methods.
Edited by: KGelling on 17-May-2012 06:10

KGelling wrote:
The best method that I've found was to add readonly="readonly" the item element, but this causes the input item to lose its APEX classes and I'd prefer a declarative solution anyway.Looks like a bug to me. However a possible explanation/justification for this behaviour is that the HTML Form Element Attributes are often used to specify a custom class for the item, so the default class is removed to prevent any conflicts. IMO APEX needs to provide declarative support for the use of multiple, space-separated class values in page, region, item etc attributes.
As a workaround in this case, just include the class in the HTML Form Element Attributes:
class="number_field" readonly="readonly"
I've created a DEMO - http://apex.oracle.com/pls/apex/f?p=READONLY - which demonstrates the 4 methods.
Thanks for making the effort.

AJAX and Read-Only Items

I used the examples from Carl Backstrom and Denes Kubicek to get my cascading select list working.
I have two select list fields (Origin and Type) that I use to determine the data to appear in a third select list field (Customer).
With help from people on this forum I was able to get things to work.
Now I have an issue when I conditionally make the Origin field "read-only".
When this occurs, data appears in my "Customer" select list on the INITIAL display of the form.
However, when I change the value in the "Type" select list field, no data appears in the Customer select list.
If I change the "Origin" field to NOT be read-only, I can change the value in the "Type" select list field and everything works OK.
I hope I have given enough information.
THANKS in advance.
Raymond

Raymond,
It looks like read-only select is really special:
(I replaced < > with [])
When select is not read-only generated html is:
[select name="p_t01" size="1" id="P1_ORIGIN_NO"
onchange="get_AJAX_SELECT_XML('P1_ORIGIN_NO','P1_DISPLAY_SSA','','','P1_CUSTOMER','CASCADING_CUSTOMER_LOV')";
[option value="%null%"]%[option]
[option selected="selected" value="001"]DOTIKI MINE[option]
[option value="S01"]ECO COAL PELLETIZATION NO. 12, LLC[option]
[select]
It means that P1_ORIGIN_NO in get_AJAX_SELECT_XML will be "001"
But when select is read-only your html code is:
[input type="hidden" name="p_t01" value="001" /]
[span id="P2_ORIGIN_NO"
onchange=
"get_AJAX_SELECT_XML('P2_ORIGIN_NO','P2_DISPLAY_SSA','','','P2_CUSTOMER','CASCADING_CUSTOMER_LOV')";
DOTIKI MINE
[span]
[pre]
P2_ORIGIN_NO in get_AJAX_SELECT_XML will be "DOTIKI MINE" which I think is wrong.
It looks like for read-only you need hidden item with code of
drop - down list or somehow you have to reach [input type="hidden" name="p_t01" value="001" /]
Lev
Message was edited by:
le

OAF: Error While Formatting a Read Only MessgeTextInput field of an AdvanceTable "$#,##0.00" format.

Hi Gurus,
Please see the below issue I am facing while formatting the field in OAF.
Situation:
Custom BidPG page extends a shared region.(sharedRN.xml)
and in SharedRN I have a advance table, with 5 columns each having MessageTextInput read only Items.
While the page is getting loaded values are coming from action fired in the PFR. and getting formatted with a $#,##0.00 format. which I have done over bean of all MessageTextInput items
using below code in process request.
Formatter formatter = new OADecimalValidater("$#,##0.00;($#,##0.00)", "$#,##0.00;($#,##0.00)");
OAMessageTextInputBean NetincPerMac = (OAMessageTextInputBean)webBean.findIndexedChildRecursive("item243");
NetincPerMac.setAttributeValue(ON_SUBMIT_VALIDATER_ATTR, formatter);
Above formatting is working for below cases.
285 becomes $285.00
230.45 becomes $230.45
But in case if there are numbers like 234.254 it will be formatted as $234.254. Here it wont set the precision to 2.
I want to display till only 2 digits after decimal.
please let me know Where I am going wrong or missing some steps to do so.
I have tried below approaches but it did not worked out for me.
          OADecimalValidater dval= new OADecimalValidater("$#,##0.00;($#,##0.00)", "$#,##0.00;($#,##0.00)");
           dval.setMaxPrecision(2);
          Formatter formatter = dval;
Also , I have tried to set Currency Code as well to USD but it didnot worked out for me.
Please let me know how we can set the precision to 2.
Please note: in process request I dont have data in the bean, I have tried writing a method in controller and setting precision to 2.but it errored out for NULL values coming from bean in process request.
Please reply. Its an urgent issue needs to be resolved.
Thanks,
Premanshu

On another link I found the following :
BKI4007E
File filename cannot be read. Reason: errno(errno number) errno text.
Explanation:
Data could not be read due to some system error. Check errno text for further information. If this error recurs, this might indicate some hardware problems.
User response:
Contact your system administrator.
The Link:
http://ezbackup.cornell.edu/techsup-v5.4/ibmdocs/messages/html/anrcms5878.htm
Regards,
Siddhesh

Value of a read only check box is always null

Hi,
I have a read-only check box in my form which fetches its values using Y or N value from table. If the value fetched from the table is 'Y' then check box is checked.
But when I tried to assign the value of this check box to some other item it is always showing null. When I made the check box editable then it started showing the value.
I appreciate if some one can share their thoughts if dealt with similar kind of issue.
Thanks in advance.
-Raj.

Read-only items often have the "disabled" attribute which prevents them from being POSTed so you can't pass their values from the browser to the application. Since you get the value from the database, why not simply fetch that value again after the page is submitted using a computation to set the other item's value?
Scott

Conditional read only radiogroup item losing value when saving

Apex 3.2
I have a radiogroup item that is set to read only after it's populated and the user is not in the ADMIN Role. When non ADMIN users edit the page, it shows the value and they cannot change it, but if they save the page, it loses the value. Works fine if the user has ADMIN role.
This is the Pl/SQL function in the "Item is read only when" section
begin
if :p3_event_detail_id is not null and :p3_notification_period_id != -1 and not apex_util.public_check_authorization('ADMIN') then
return true;
else
return false;
end if;
end;
There is also a Not Null validation on this radiogroup item.
I changed the item type to select list and it works fine, but user like the radiogroup button.
Any ideas?

It's using a shared component LOV cleverly called LOV_YN which consists of a static LOV with
1 Display=Yes, Return=Y
2 Display=No, Return=N
The settings in the LOV section on the item iteself:
Named LOV: LOV_YN
Display Extra values: No Dynamic translation: Not translated
Number of columns: 2 Display null: No
Null display value is blank as is null return value
Item was setup as a radio group and was only converted over to a select list to work around this issue. Let me know what else you need and thanks again.
Rgds/Mark M.

LOV Displays the Return Value when Read Only

Greetings,
I searched for a question/answer for this, but didn't find this exact scenario mentioned, but I may have missed it. If you know of this already been asked/answered just point me to the thread.
On APEX version - 4.1.1.00.23
I have a LOV that is populated by a dynamic action from another LOV. That works great. Depending on the value of another page item the 2nd LOV is Editable or Read Only. The problem is that when the 2nd LOV is Read Only the result value (an ID) displays instead of the display value.
1 - Why is this?
2 - How do I prevent this from happening?
Also, I don't want 2 separate page items (one for edit, one for display) for the 2nd LOV, because the 2nd LOV also has a dynamic action on it to populate a 3rd LOV. The population of the 3rd LOV works great, whether the 2nd LOV is editable or read only.
= = = = = = = 2nd LOV SQL = = = = = = =
select sub_com_desc||' - '||commodity_desc d, defect_code_header_id r
from qcis_defect_code_header
where inactive_date IS NULL and plant_id = :P10_PLANT_ID
order by sub_com_desc
= = = = = = = = = = = = = = = = = = = =
Thanks, Tony
Edited by: cloaked on May 8, 2013 12:11 PM

I've decided to try a different approach. Since the Select List LOV was Read Only and not populating correctly it was causing a session state error when inserting the row. So, I've made the Select List LOV editable, but it shouldn't be. I now need to disable the page item using JavaScript to prevent it from being changed. I need to do so only when a page item contains a certain value.
Will someone share an example of JavaScript snippet of code I need to use? (I'm not much of a JavaScript coder.)
The page item I need to disable is named - P10_DEFECT_HEADER_ID
I need to disable it when P10_MAP_TYPE = 'P'
Thanks, Tony
Edited by: cloaked on May 15, 2013 1:00 PM

Select item on a Tabular form with a different dynamic LOV on each row

I would like to use a tabular form where one of the columns is a dynamic LOV based Select, and where that dynamic LOV refers to one of the column values on each row.
So if the tabular form represented a list of teams and the LOV-based Select column was the current team leader, I would want that select list to be populated only with the members of that team (different for each row). Since the list of team members is in some other table (all_players or something) I would want to populate the LOV with a query with a where clause that selected only those players records with a team-membership equal to the current tabular form's team id. So, on each row that select list's contents would be different.
-- Justin

I'm beating a dead horse here but I did get something to work with "less" code. My current needs do not require me to cascade drop downs, I only want 1. You can use the query like the in the first reply (but I don't have a table with joins) I created a simple two column table dept_emp with 4 records 10,null 20,null .... I want to fill the nulls with an employee but ONLY an employee that matches the dept. (Same concept of team leader and members).
Here's the query:
select apex_item.display_and_save(1,dept) dept,
apex_item.select_list_from_query(2, name, 'select ename from emp where deptno='||dept) name
from dept_emp
I removed the code that was there already (ApplyMRU) and just put in this code:
BEGIN
FOR i IN 1..HTMLDB_APPLICATION.G_F01.COUNT LOOP
UPDATE dept_emp
SET
name=HTMLDB_APPLICATION.G_F02(i)
WHERE dept=to_number(HTMLDB_APPLICATION.G_F01(i));
END LOOP;
END;
The G_F01 matches the column 1 and so forth. There's more documentation but little explanation at:
http://download.oracle.com/docs/cd/B25329_01/doc/appdev.102/b25309/api.htm#sthref2171
The thing I could not get to work was a dynamic message
#MRU_COUNT# row(s) updated, #MRI_COUNT# row(s) inserted.
Not sure when the MRU_COUNT gets populated (probably in the routine I removed ;))
You're probably way past me by now but I like to have as little code as possible when it comes to maintaining an app. That's why I liked oracle forms so much. This kind of stuff was pretty easy to do.
Thanks again everybody!

Read-only table with a LOV on a VO's attribute

Hi,
I have a VO ('X') that is displayed as a read-only table. 'X' has an attribute called 'SubscriptionId'. The value of 'SubscriptionId' is a foreign key to another table called 'Subscription'. My 'Subscription' database table has a column named 'Description'.
Example:
'X' has an attribute 'SubscriptionId' = 14
DB table 'Subscription' has a row that looks like this:
14, "A subscription description" (where "A subscription description" is the 'Description' column)
I set up a LOV for 'SubscriptionId' on my VO 'X', so that it should show the value of 'Description' from 'Subscription' instead of the 'SubscriptionId'.
If I display my VO 'X' as a form, I can see my LOV (for 'Description').
However, when I display my VO ('X') as a read-only table, it isn't adhering to the LOV I defined on my VO, and is instead showing the 'SubscriptionId'.
What do I need to do differently on my table to show the 'Description' instead of the foreign key 'SubscriptionId'? I want it to be just an output text of the Description, not a choice list.
Thanks,
Joel

Hi
In simple way just set the ReadOnly property of choice list in the coloum = true
for example
<af:column sortProperty="EmpId" sortable="true"
headerText="#{bindings.DocTransactionView1.hints.EmpId.label}"
id="c2" align="center">
<af:selectOneChoice value="#{row.bindings.EmpId.inputValue}"
label="#{row.bindings.EmpId.label}"
required="#{bindings.DocTransactionView1.hints.EmpId.mandatory}"
shortDesc="#{bindings.DocTransactionView1.hints.EmpId.tooltip}"
id="soc4" readOnly="true">
<f:selectItems value="#{row.bindings.EmpId.items}" id="si3"/>
</af:selectOneChoice>
</af:column>

Making a dynamically generated field as Read Only

Hi All,
I am extending a standard CO and in that I wanted to make an entire table as read only. I checked by personalizing the page from front end, but as the items are dynamically generated fields , they are not visible in personalize page.
So is there any way to cach these fields and make them read only programmatically.
Thanks,
Srikanth

Hi Pratap,
I have looked into the view source and took the name of a input type ( There is no ID for the field) and used it in findIndexedChild, but it returns a null. I guess this is happening is the current CO is a mere region level CO and it is not being given the access.
The code in the class file is as follows :
public static void processTable(OAPageContext oapagecontext, OAWebBean oawebbean)
oapagecontext.startTimedProcedure("CrossTableCO", "processTable");
String s = null;
String s1 = null;
int i = oawebbean.getIndexedChildCount();
String as[[][]] = new String[7];
int j = 0;
String as1[[][]] = new String[i][6];
for(int k = 0; k < oawebbean.getIndexedChildCount(); k++)
UINode uinode = oawebbean.getIndexedChild(k);
if(!(uinode instanceof OAMessageStyledTextBean))
continue;
OAMessageStyledTextBean oamessagestyledtextbean = (OAMessageStyledTextBean)uinode;
if(oamessagestyledtextbean.isRendered())
oamessagestyledtextbean.setRendered(false);
oamessagestyledtextbean.setAttributeValue("benCustomBeanRender", "Y");
if("TotalPlanLabel".equals(oamessagestyledtextbean.getUINodeName()))
s1 = oamessagestyledtextbean.getLabel();
continue;
if(s == null)
s = oamessagestyledtextbean.getViewUsageName();
as[j][0] = oamessagestyledtextbean.getViewAttributeName();
as[j][1] = oamessagestyledtextbean.getSortByAttributeName();
as[j][2] = oamessagestyledtextbean.getLabel();
as[j][3] = oamessagestyledtextbean.getExportByViewAttrName();
as[j][4] = oamessagestyledtextbean.getDestination();
as[j][5] = oamessagestyledtextbean.getUINodeName();
as[j][6] = oamessagestyledtextbean.getDataType();
if(as[j][4] != null && as[j][5] != null)
as1[j][0] = as[j][5];
as1[j][1] = as[j][0];
as1[j][2] = s;
as1[j][3] = as[j][4];
as1[j][4] = as[j][6];
as1[j][5] = as[j][3];
j++;
continue;
if("TotalPlanLabel".equals(oamessagestyledtextbean.getUINodeName()))
s1 = "XXHideXXTotalXX";
oawebbean.setAttributeValue("CrossTableUpdateInfo", as1);
oawebbean.setAttributeValue("CrossTableRenderCount", Convert.getString(j));
if(s == null)
return;
OAViewObject oaviewobject = (OAViewObject)oapagecontext.getApplicationModule(oawebbean).findViewObject(s);
if(oaviewobject == null || !oaviewobject.isPreparedForExecution() || oaviewobject.first() == null)
return;
} else
oawebbean.addIndexedChild(createTable(oawebbean, oaviewobject, as, j, s1));
oawebbean.setAttributeValue("CrossTableRowCount", Convert.getString(oaviewobject.getRowCountInRange()));
oapagecontext.endTimedProcedure("CrossTableCO", "processTable");
return;
private static UINode createTable(OAWebBean oawebbean, OAViewObject oaviewobject, String as[][], int i, String s)
int j = oaviewobject.getRowCountInRange();
DataTextNode datatextnode = new DataTextNode(new DataBoundValue("text"));
String as1[] = new String[j + 1];
CrossTableData acrosstabledata[] = new CrossTableData[i];
int k = -1;
for(int l = 0; l < i; l++)
acrosstabledata[l] = new CrossTableData(new CrossTableCellData[j + 1]);
for(int i1 = 0; i1 <= j; i1++)
if(i1 > 0)
try
if(s != null && j > 1 && CT_NUM_MINUS_ONE.equals(oaviewobject.getRowAtRangeIndex(i1 - 1).getAttribute("GroupOiplId")))
as1[i1] = s;
else
as1[i1] = (String)oaviewobject.getRowAtRangeIndex(i1 - 1).getAttribute("Name");
catch(Exception exception)
datatextnode = null;
as1[i1] = "";
if(k < 0 && j > 1 && "XXHideXXTotalXX".equals(s) && CT_NUM_MINUS_ONE.equals(oaviewobject.getRowAtRangeIndex(i1 - 1).getAttribute("GroupOiplId")))
k = i1;
for(int j1 = 0; j1 < i; j1++)
if(i1 == 0)
acrosstabledata[j1].getData()[i1] = new CrossTableCellData(as[j1][2]);
else
acrosstabledata[j1].getData()[i1] = new CrossTableCellData(null, as[j1][2], oaviewobject, i1 - 1, as[j1][0], as[j1][1], as[j1][3], as[j1][4], as[j1][5], as[j1][6]);
TableBean tablebean = new TableBean("CrossTable", new ArrayDataSet(acrosstabledata), null, null, datatextnode, new ArrayDataSet(as1, "text"));
tablebean.setWidth("100%");
tablebean.setSummary(" ");
tablebean.setNameTransformed(false);
tablebean.setTableFormat(new DictionaryData("tableBanding", "rowBanding"));
tablebean.setID((new StringBuilder()).append("CrossTable").append(oawebbean.getID()).toString());
oawebbean.setAttributeValue("CrossTableId", tablebean.getID());
DictionaryData adictionarydata[] = new DictionaryData[j + 1];
Object obj = null;
Object obj1 = null;
for(int k1 = 0; k1 <= j; k1++)
OAWebBean oawebbean1 = createColumn(k1);
if(k1 == k)
oawebbean1.setRendered(false);
tablebean.addIndexedChild(oawebbean1);
if(k1 == 0)
adictionarydata[k1] = new DictionaryData("columnDataFormat", "textFormat");
continue;
try
String s1 = (String)oaviewobject.getRowAtRangeIndex(k1 - 1).getAttribute("TextFormat");
if("Y".equalsIgnoreCase(s1))
adictionarydata[k1] = new DictionaryData("columnDataFormat", "textFormat");
else
adictionarydata[k1] = new DictionaryData("columnDataFormat", "numberFormat");
catch(Exception exception1)
adictionarydata[k1] = new DictionaryData("columnDataFormat", "numberFormat");
tablebean.setColumnFormats(new ArrayDataSet(adictionarydata));
return tablebean;
private static OAWebBean createColumn(int i)
OAFlowLayoutBean oaflowlayoutbean = new OAFlowLayoutBean();
OAMessageTextInputBean oamessagetextinputbean = new OAMessageTextInputBean();
OAMessageStyledTextBean oamessagestyledtextbean = new OAMessageStyledTextBean();
OAMessageDateFieldBean oamessagedatefieldbean = new OAMessageDateFieldBean();
OASwitcherBean oaswitcherbean = new OASwitcherBean();
Hashtable hashtable = new Hashtable();
hashtable.put("CtPPRTrgCol", new DataBoundValue(new CrossTableColumnData(i, "Name")));
oaswitcherbean.setNamedChild("input", oamessagetextinputbean);
oaswitcherbean.setNamedChild("date", oamessagedatefieldbean);
oaswitcherbean.setChildNameBinding(new CrossTableColumnData(i, "Render"));
oaflowlayoutbean.addIndexedChild(oaswitcherbean);
oaflowlayoutbean.addIndexedChild(oamessagestyledtextbean);
oamessagetextinputbean.setNameBinding(new CrossTableColumnData(i, "Name"));
oamessagetextinputbean.setTextBinding(new CrossTableColumnData(i, "Text1"));
oamessagetextinputbean.setAttributeValue(DESCRIPTION, new DataBoundValue(new CrossTableColumnData(i, "Label")));
oamessagetextinputbean.setAttributeValue(COLUMNS_ATTR, "12");
oamessagetextinputbean.setAttributeValue(PRIMARY_CLIENT_ACTION_ATTR, OAWebBeanUtils.getFirePartialActionForSubmit(oamessagetextinputbean, null, "update", hashtable, null));
oamessagetextinputbean.setDataType("NUMBER");
oamessagetextinputbean.setAttributeValue(READ_ONLY_ATTR, new DataBoundValue(new CrossTableColumnData(i, "ReadOnly")));
oamessagetextinputbean.setAttributeValue(ON_SUBMIT_VALIDATER_ATTR, new DataBoundValue(new CrossTableColumnData(i, "SubmitValidator")));
oamessagedatefieldbean.setNameBinding(new CrossTableColumnData(i, "Name"));
oamessagedatefieldbean.setTextBinding(new CrossTableColumnData(i, "Text1"));
oamessagedatefieldbean.setValueBinding(new CrossTableColumnData(i, "Text1"));
oamessagedatefieldbean.setAttributeValue(DESCRIPTION, new DataBoundValue(new CrossTableColumnData(i, "Label")));
oamessagedatefieldbean.setAttributeValue(COLUMNS_ATTR, "12");
oamessagedatefieldbean.setAttributeValue(PRIMARY_CLIENT_ACTION_ATTR, OAWebBeanUtils.getFirePartialActionForSubmit(oamessagedatefieldbean, null, "update", hashtable, null));
oamessagedatefieldbean.setDataType("DATE");
oamessagedatefieldbean.setAttributeValue(READ_ONLY_ATTR, new DataBoundValue(new CrossTableColumnData(i, "ReadOnly")));
oamessagestyledtextbean.setTextBinding(new CrossTableColumnData(i, "Text2"));
return oaflowlayoutbean;
Pls let me know for any clarifications.
Thanks,
Srikanth

Making Read Only A select List Item

Hi,
I am using Application Express 3.1.1.00.09 version.
If the date field is future date then the Select List field should become Read only.
I tried to make "read only".
When I made it "read only" '>[] is displayed???
Does some one have a solution?
Thanks,
Priyanka.

Hi Leckraj,
I assume that
the select list is not displayed at all.means that your page item is not rendered as a select list input control, but it's rendered as text only, right? That's the nature of the read only condition, it will render almost all controls as text only.
About the dynamic action solution. That can be simplified and doesn't require a hidden item or JavaScript.
1) Create a dynamic action which fires for the "Page Load" event
2) As (Server Side) Condition Type set "exists (SQL quer returns...)" and specify your SQL statement
3) Use a "Disable" action to disable your select list page item
The above dynamic action will only be included and executed on the page, if the SQL statement returns a value.
Note: Please keep in mind that dynamic actions are browser based operations, for a skilled user it's no problem to enable the select list and modify the value. To secure it you should add a server side validation to verify if the user is really allowed to modify the value. That's the difference to the "Read Only Condition", because in that case the APEX engine guarantee that the value can't be modified.
Regards
Patrick
Member of the APEX development team
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Item Selection on a dynamic LOV (SQL Query)

Hi,
I've a dynamic LOV with an SQL query who return a list of data (one column). When i select a data in this LOV to be use as an item (sql query) in the same page the data is always null. In debug mode substitution string is null.
FYI : when the data is selected, a button is clik to perform an sql query for a report in another page.
Thanks. Sorry Abasolute beginner
Message was edited by:
user581765

Thanks for Your help.
The date is in fact a CHAR display (not really a date) so that is not the error.
For your information when i select a row in the list (format char YYYYMMDD_HHMM) it seems that Apex do not catch my select in the Session state.
I've change the item name with P2_DATE_FLOW but the problem remain.
This is the debug log if can help
0.03: Application 114, Authentication: CUSTOM2, Page Template: 3644802034190382
0.06: ...Session ID 1868105032215374 can be used
0.06: ...Application session: 1868105032215374, user=Neop
0.06: ...Determine if user "Neop" workspace "2859608277950243" can develop application "114" in workspace "2859608277950243"
0.06: Session: Fetch session header information
0.06: ...Metadata: Fetch page attributes for application 114, page 3
0.06: Fetch session state from database
0.06: Branch point: BEFORE_HEADER
0.06: Fetch application meta data
0.08: Computation point: BEFORE_HEADER
0.08: Processing point: BEFORE_HEADER
0.08: Show page template header
0.08: Computation point: AFTER_HEADER
0.08: Processing point: AFTER_HEADER
0.08: Computation point: BEFORE_BOX_BODY
0.08: Processing point: BEFORE_BOX_BODY
0.08: Region: Report 1
Report 1
0.08: show report
0.09: determine column headings
0.09: parse query as: CFM_MDRE
0.12: binding: ":P2_DATE_FLOW"="P2_DATE_FLOW" value="0"
0.14: print column headings
0.14: rows loop: 15 row(s)
No data found.

Read only item populated by dynamic LOV

Similar Messages

Maybe you are looking for