LOVs in Detail Table

Hi
I've been generanting pages with LOVs in table layouts, I have an specific problem with LOVs in forms with two tables in the same page (one master and the other details, its generated with the option master and detail on Same PAge). The first table (master) is readonly and the second table (detail) is editable. The second table have an LOV, but it doesn't work.
The problem is the following when trying to insert a record: the user click on LOV icon, the window is opened and the user select a value, the window LOV is closed but the value selected (display value) is not displayed in the text field, it continues always blank.
When trying to update a record: the user click on LOV icon, the window is opened and the user select a value, the window LOV is closed but the value selected is not displayed in the text field, it still displayed the old value.
The master deail structure is very simple, I reproduce the mistake two times with diferents tables. What would be the problem? May I use LOVs in master-detail tables?
Thanks in advance
Liceth

Liceth,
Using JHeadstart 10.1.2.0.20, I could not reproduce the problem with the following settings:
Master: DepartmentsView - Table Layout - no insert/update/delete - no 'newrows'
Detail: EmployeesView - Table layout (same page) -insert-update-delete allowed - newrows =2
Lookup on Employees: JobsLookup: type = lov, all attributes (base + lookup) on JobId.
Could you try this and indicate what I should change to this situation to reproduce the problem?
Kind regards,
Peter Ebell
JHeadstart Team

Similar Messages

Multi-row insert in master-detail tables

Hi, I'm using jdev 10.1.3.2 with jheadstart and my problem is:
I hava a master-detail structure, both are tables and my goal is that I want multi insert (exactly 3) in master and detail table when user makes new order(some business scenario). I cannot create rows in master or detail VO by overriding create() method because its entities have complex primary keys and some part of this key is populated by the user with lov. So I set in jhs new rows to 3 and checked multi-row insert allowed but the problem is that overall I can only create rows in master table after I submit form. I want to create row in master table and fill rows in detail table, and after that I want to have opportunity to create second (or even third) row in master table and fill rows in detail table.
thanks for help.
Piotr

See JHS DevGuide: 3.2.1. Review Database Design:
If you are in the position to create or modify the database design, make sure all
tables have a non-updateable primary key, preferably consisting of only one
column. If you have updateable and/or composite primary keys, introduce a
surrogate primary key by adding an ID column that is automatically populated.
See section 3.2.4 Generating Primary Key Values for more info. Although ADF
Business Components can handle composite and updateable primary keys, this
will cause problems in ADF Faces pages. For example, an ADF Faces table
manages its rows using the key of the underlying row. If this key changes,
unexpected behavior can occur in your ADF Faces page. In addition, if you want
to provide a drop down list on a lookup tables to populate a foreign key, the
foreign key can only consists of one column, which in turn means the referenced
table must have a single primary key column.
Groeten,
HJH

[BUG] LOV inside AF:table doesn't return value

Hi,
I am using JDEV TP4.
I have a LOV inside a af:table.
<af:column sortProperty="LaoId" filterable="true"
sortable="true"
headerText="#{bindings.Packstuecke0012.hints.LaoId.label}"
id="collaoid"
partialTriggers="collagercode">
<af:inputListOfValues id="laoIdId"
popupTitle="Search and Select: #{bindings.Packstuecke0012.hints.LaoId.label}"
value="#{row.bindings.LaoId.inputValue}"
model="#{row.bindings.LaoId.listOfValuesModel}"
required="#{bindings.Packstuecke0012.hints.LaoId.mandatory}"
columns="#{bindings.Packstuecke0012.hints.LaoId.displayWidth}"
shortDesc="#{bindings.Packstuecke0012.hints.LaoId.tooltip}"
partialTriggers="lagerCodeId">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.Packstuecke0012.hints.LaoId.format}"/>
</af:inputListOfValues>
</af:column>
After selecting a value in the LOV and leave the LOV the id in the corresponding column field doesn't change.
Same LOV outside of table works fine.
Any suggestions?
regards
Peter

Hi,
Ok, I try to explain the problem more detailed:
1) I have a model driven LOV (af:inputListOfValues) within a af:table column
2) LOV is based on view and shows the id "LagerCode"
3) Navigate to view object in the model select "Attributes" on the left side and double-click on the attribute "LagerCode"
4) This opens the dialog "edit Attribute: LagerCode"
5) navigate to register "UI-Hints"
6) And here is the important step: UNSELECT the checkbox "Query List Automatically".
7) Run the application and open the LOV --> The LOV list is empty (because of step 6)
8) Execute "search" in the LOV and select any value
9) PROBLEM: No value is returned to af:inputListOfValues
If I do the same steps with a LOV outside of af:table everything is OK.
If I do NOT UNCHECK the checkbox "Query List Automatically" in step 6 than the LOV list is queried as soon as the LOV dialob opens. In this case the selected value from the LOV list will be returned to af:inputListOfValues.
I hope you are able to follow my steps and you can reproduce the problem.
regards
Peter

Inconsistent inserts into detail table of master-detail form

Hello,
[I am not sure if this is a bug or user error, so I've also put this in the bug tracking system. Apologize for the 'duplication']
I have a master-detail form: Orders is the master, and Order_Details is the detail. I have noticed some inconsistent behavior when inserting the detail information.
On occasion, the row will be inserted, and a null value will get inserted into the database for the first column of the detail table; all the other data values will be inserted fine. There doesn't seem to be any pattern to when it happens. I wrote down the following test steps:
1. Enter new order information and click 'Create'
2. Click 'Add Row' button so can add order detail info
3. Enter detail row information
4. Click 'Add Row' (I do this so I can see the success message that the detail data was actually inserted)
5. Click 'Apply Changes' at the master level.
I ran a query on the order details table and saw that the data inserted correctly. Then I ran the following test:
1. Enter new order information and click 'Create'
2. Click Add Row button so can add order detail info
3. Enter detail row information
4. Click 'Add Row' (success message appears that detail was inserted)
5. Enter second detail row information
6. Click 'Add Row' (success message appears that detail was inserted, however, now in the first column of that second detail row - the product name field/column - the data does not appear. I only see my null text value. The data in the first detail row is all correct)
7. Enter third row detail information
8. Click 'Add Row' (success message appears that detail was inserted, and this row's information appears correctly, as does the first row's, but the second row is still showing a null value for the product name column)
9. Click 'Apply Changes' to get out of the form
A query of the order details table shows that a null value (-) has indeed been inserted into the table for the product name column of the second detail row.
This behavior also happens when I don't have a null value for the LOV (i.e., it defaults to the first row of the lookup table).
Has anyone seen this before? Am I entering the data incorrectly?
Thanks.
-melissa
Message was edited by:
mblakene

having the some problem. Any help with this ??
milowski were you able to solve it ? can you share the information.
Thanks

LOV Master detail where clause

Hi.
JDeveloper 11.1.1.2
It seem to be impossible to have a master / detail with a LOV on the the detail block, where the LOV it self is another detail of the same master.
That is - the content of the LOV is wanted to depend on the master.
The result is that the LOV is empty.
Does anyone know why?
/Erik

from my understandings,
you get the one of the field data present in parent table, fetch that data as lov in child table.
if am get you right means,
The result is that the LOV is empty.you are not yet commiting the parent table. so the result is not getting detail table field lov.
if you are commiting the table. you may get it.

How to populate rows in the detail table of a form from another table.

please can someone help me here:
i have a master/detail page. the master data is created and then i would like to do this: when one goes to the detail page (when first created), i would like somehow to populate all the rows in the detail table from rows retrieved in another table (with conditions).
i am new to apex so if this is a stupid question i apologise in advance!

Hi
Firstly, there are no stupid questions, we all start somewhere!
However, I could do with some more detail (or even better an example on apex.oracle.com). Please can you post exactly what you have so far and what you want to achieve with simple details of the tables involved.
It sound like you may need to create a custom process to populate the details. You say 'with conditions'... what conditions?
Cheers
Ben
http://www.munkyben.wordpress.com
Don't forget to mark replies helpful or correct ;)

ADF Faces Query Panel: How to display master data in detail table?

Before stating the question, here is the background:
I've a Fusion ADF (model/viewController) app that includes 2 tables with a master-detail relationship. The master table stores error numbers and associated levels of logging severity; the detail table stores the actual message text. These need to be separate, related tables because the requirement is that message text for a given error number can vary by product release.
Messages are added in a bounded task flow; data for the master table entered in 1 fragment, data for the detail table in a 2nd page fragment. In the app, the Entity Objects for these tables are related with a foreign key association and have a composition association. This was done because the error numbers are generated in an Oracle DB sequence, and from what i have read that is a way in a task flow to have ADF put the number generated for the master table into the related key of the child table.
The question is this:
I need to create an ADF query panel with a table that searches on the detail DB table. However, i also need to use a couple of fields from the master DB table in both the query and in the ADF table. In addition, I need to add the ability for the user to edit either the master or detail record for the row he/she selects in the ADF table. I know how to create a view that would display the info i need; however, i have not been able to figure out how to obtain the keys for the selected ADF table row and pass them to the task flows that would edit.
The master table has a numeric primary key. The detail table primary key consists of a foreign key to the master key and also a release number.
I'm new to ADF and have been struggling with how to do this: i've a workaround that is functional but too klunky to be a permanent solution. So, could someone point me to some information on how to accomplish this?
Versions: JDeveloper 11.1.1.4, ADF Business Components 11.1.1.59.23
Thanks for your help!

Thanks. I tried this out, but ran into an issue in that the detail table has 2 keys - a foreign key to the master primary key, and a 2nd key that uniquely distinguishes the detail. So i tried various things centered around using the SetCurrentRowWithKey operation and trying to obtain the selected ADF table row using an EL OF #{data.<pageDef>.<Iterator>.currentRowKeyString}; however i could not get the detail record for the selected row to display.
I did find another approach that worked - I am wondering, is there anything problematic with this approach?:
1. Create a VO joining the Master and Detail tables, with the Detail table being updatable.
2. Made sure the applicable attributes were defined as keys.
3. Add a query panel w/table using this VO.
4. Create an ADF form based on the VO, showing the updatable fields.
5. Create a bounded task flow with the following set on the Behavior tab:
a. Share data controls with calling task flow
b. Always Begin Transaction
I specifically am wondering whether "Share data controls with calling task flow" has any negative implications or gotchas to handle. The doc at http://download.oracle.com/docs/cd/E21764_01/web.1111/b31974/taskflows_parameters.htm#ADFFD1693 doesn't suggest so, but just wanted to double-check before I go down this path.

ADF master-detail master selection not updating detail tables properly

Hi All,
I am using JDev version : 11.1.2.0.0
I created new Fusion Web Application Module. In that module I created a master-detail data model and added them to a page fragment with a query panel. When I run it as a separate module, It works perfectly and Master selection correctly updates detail tables.
But when I integrate that module to another Fusion Application(Add application jar file to the Master Application libraries), Master-details master selection not updating detail tables properly. This problem occurred sequentially.
The problem is that.
After the page load, first selection of the Master Table works correctly and detail tables update correctly.
But second selection doesn't work, means detail table doesn't get update according to the Master table.
And again in the third selection works correctly.
This happens in a sequential manner. I monitor the behavior using Firebug. Observations are as follows,
When running correctly, Response of the Post Definition is
<?xml version="1.0" ?> <partial-response><changes><update id="pt1:t1"><![CDATA[<div tabindex="0" id="pt1:t1" class="xpa xpi" _leafColClientIds="['pt1:t1:c1','pt1:t1:c2','pt1:t1:c3','pt1:t1:c4','pt1:t1:c5','pt1:t1:c6','pt1:t1:c7','pt1:t1:c8','pt1:t1:c9','pt1:t1:c10','pt1:t1:c11','pt1:t1:c12','pt1:t1:c13']"><div id="pt1:t1::ch" style="overflow:hidden;position:relative;width:1365px;" _afrColCount="13" class="xz4"><table class="xz6" summary="This table contains column headers corresponding to the data body table below" id="pt1:t1::ch::t" style="position:relative;table-layout:fixed;width:1365px" cellspacing="0"><tr><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th></tr><tr><th id="pt1:t1:c1" _d_index="0" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c1::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DateFormat</div></th><th id="pt1:t1:c2" _d_index="1" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c2::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DefinisionId</div></th><th id="pt1:t1:c3" _d_index="2" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c3::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldId</div></th><th id="pt1:t1:c4" _d_index="3" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c4::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLabel</div></th><th id="pt1:t1:c5" _d_index="4" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c5::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLength</div></th><th id="pt1:t1:c6" _d_index="5" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c6::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOffset</div></th><th id="pt1:t1:c7" _d_index="6" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c7::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOrder</div></th><th id="pt1:t1:c8" _d_index="7" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c8::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldStatus</div></th><th id="pt1:t1:c9" _d_index="8" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c9::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldType</div></th><th id="pt1:t1:c10" _d_index="9" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c10::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldTypeLen</div></th><th id="pt1:t1:c11" _d_index="10" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c11::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IgnoreField</div></th><th id="pt1:t1:c12" _d_index="11" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c12::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IsMandatory</div></th><th id="pt1:t1:c13" _d_index="12" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c13::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">RecordType</div></th></tr></table></div><div id="pt1:t1::db" class="xyx" style="position:relative;width:100%;overflow:hidden" _afrColCount="13"></div><div id="pt1:t1::sm" class="xzt" style="position:absolute;display:none"></div><div id="pt1:t1::ri" class="xyz" style="position:absolute;display:none;overflow:hidden"></div><div id="pt1:t1::dataW" style="display:none"></div></div>]]></update><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="d1::iconC"><![CDATA[<span id="d1::iconC" style="display:none"><span id="af_table::disclosed-icon"></span><span id="af_table::undisclosed-icon"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval><![CDATA[AdfPage.PAGE.sendStreamingRequest("pt1:t1");]]></eval><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/dnd-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/nav-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/menu-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/table-SHERMAN-1147.js</extension><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){ self.location = "mcsd.html"; }</eval><eval><![CDATA[AdfDhtmlLookAndFeel.addSkinProperties({"af|table-tr-column-scroll-animation-duration":"300","af|table-tr-column-reorder-animation-duration":"600","af|table-tr-hover-highlight-row":"true"});AdfPage.PAGE.addComponents(new AdfRichTable('pt1:t1',{'rowSelection':'single','rowBandingInterval':0,'editingMode':'none','afrSelListener':true}),new AdfRichColumn('pt1:t1:c1',{'sortProperty':'DateFormat','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c2',{'sortProperty':'DefinisionId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c3',{'sortProperty':'FieldId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c4',{'sortProperty':'FieldLabel','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c5',{'sortProperty':'FieldLength','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c6',{'sortProperty':'FieldOffset','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c7',{'sortProperty':'FieldOrder','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c8',{'sortProperty':'FieldStatus','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c9',{'sortProperty':'FieldType','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c10',{'sortProperty':'FieldTypeLen','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c11',{'sortProperty':'IgnoreField','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c12',{'sortProperty':'IsMandatory','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c13',{'sortProperty':'RecordType','sortable':true,'minimumWidth':12,'rowHeader':false}));AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
When not running correctly, Response of the Post Definition is
<?xml version="1.0" ?> <partial-response><changes><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){ self.location = "mcsd.html"; }</eval><eval><![CDATA[AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
I could not figure out what went wrong when integrating to another module.
Can you please help me to rectify this problem.
Thanks
dk

Hi,
sound to be an implementation specific issue that is hard to comment on without knowing how to reproduce it. If you have a rerooducible test case based on the Oracle HR schema using JDeveloper 11.1.1.6, zip it up, rename the "zip "extension to "unzip" and sent it to the mail address you find in my OTN profile. If you don't have that test case, explain how this can be reproduced
Frank

Null value in detail table's primary key

I use Business Components Data Form to define a master-detail java panel.
I don't display the primary key column in the detail grid control.
Then I click on "+" to add a row, enter a value (the 2nd part of the detail table's primary key) and click commit.
I get an error saying that the primary key column that's not displayed is null and the row cann't be committed.
How do I fix this error?

My fields are varchar2's.
-- simplified to protect the guilty:
-- (made up from memory, so sql keywords may --be misspelled, but you get the idea)
create table proj (
proj varchar2(10) not null,
constraint proj_pk
primary key(proj)
insert into proj values ('abc');
commit;
-- this table has legal values for -- the master.legal field.
-- in master, legal was changed to a -- ComboBoxControl control from -- TextFieldControl that the wizard -- generated.
create table legal_values (
proj varchar2(10) not null,
legal varchar2(10) not null,
display_order integer not null,
constraint legal_values_pk
primary key (proj, legal)
insert into legal_values
values ('abc', 'one', 1);
insert into legal_values
values ('abc', 'two', 2);
insert into legal_values
values ('abc', 'three', 3);
commit;
create table master (
proj varchar2(10) not null,
masterKey varchar2(15) not null,
legal varchar2(10) not null,
constraint master_pk
primary key (proj, masterKey)
create table detail (
proj varchar(10) not null,
masterKey varchar(15) not null,
detailkey varchar(10) not null,
display_order integer not null,
status varchar2(12) not null, -- user can only update this field
constraint detail_pk
primary key(proj, masterkey, detailkey)
-- legal rows for detail table
create table detail_values (
proj varchar2(10) not null,
detailkey varchar2(10) not null,
display_order integer not null,
constraint detail_values_pk
primary key(proj, detailkey)
insert into detail_values values
('abc', 'status a', 1);
insert into detail_values values
('abc', 'status b', 2);
commit;
-- if their is a foriegn key on details back
-- to master, then you get the
-- "mutating table" error when trigger
-- occurs.
create or replace trigger master_tr
after insert on master
for each row
begin
insert into detail
(masterKey, detailKey, status, display_order, status)
select :new.masterkey, detail_key, display_order, ' '
from detail_values;
end;
-- detail.status is a comboboxControl getting --its values of of another db table too.
-- there's also "after update" triggers on master and detail tables that copy the record to master_history and "detail_history" tables if the corresponding table is modified. Thus we have a history of the changes made to the records. The 2 history tables have 2 additional fields than their parents, "modified_date date default sysdate not null" and "modified_by varchar2(30) default user not null" that record when and who made the change. There's also a change type field that records where the change is an insert, delete or update (there 3 triggers per table , so we can correctly record change type as being insert, delete or update into the change_type field).
If you want to make it more real to life, the status value is initially blank, then can be changed to a legal status value (complete or not complete), but can not be changed back to blank.
***P.S. I have to have this ready for production by monday.****
P.P.S After you reply and change to ComboBoxControls in 2 places, try changing the table names and/or the column names (say to follow the DBA's naming convention) or add another field to the composite primary key (and unstated foriegn key) (using drop table/create table). Now try getting the existing code to run. No writing down the old/new table (or column) name pair names. Just run the code and try to fix the code based on the error messages. Are the error messages giving you adequate information to find the problem?

ADF Master Table, Inline Detail Table - How to Scroll Range/Disclose Row

JDev 10.1.3.2 ADF/BC
I really need some help here. I've tried as many things as I could think of and I still cannot get this to work.
Scenario: I have query/result page. User clicks a link in the result table to take him to another page. This page has a Master table, Inline detail table component (bound to a tree in the pageDef). Before the page renders, all I want to do is scroll the Master table to the current row (based on the previous query/result via invokeAction in pageDef) and disclose the inline detail. Simple, right? In addition, I'll need to scroll the inline detail to the current row as well.
I would like to do this prior to the components rendering but would be interested in any coding to scroll and disclose.
Thanks in advance,
Tom

I've come up with a solution to my problem. Unfortunately I'm not able to manipulate the table prior to rendering but this solution is probably the closest I'm going to get. Here is my code:
I set up a af:poll component to fire once on my jspx.
    public void poll_PollListener(PollEvent pollEvent) {
        if (this.getFromProcess("unitRowKeyValue") != null) {
            int curIndx = this.getIteratorBinding("UnitsIterator").getRowSetIterator().getCurrentRowIndex();
            this.getUnitTree().setFirst(curIndx);
            if (this.getFromProcess("systemRowKeyValue") != null) {
                this.getUnitTree().setRowIndex(curIndx);
                DisclosureEvent de = new DisclosureEvent(this.getUnitTree(), true);
                this.getUnitTree().queueEvent(de);
            this.storeOnProcess("renderPoll", false);
    }The setFirst method scrolls the table to the index specified. If the user, in my case, has selected a detail item (system), I want to disclose the detail. First I need to setRowIndex to the current index and then I fire a disclose event.
    public void unitTreeDisclosureListener(DisclosureEvent disclosureEvent) {
         if (disclosureEvent.isExpanded()) {
             CoreTable coreTable = (CoreTable)disclosureEvent.getSource();
             RowKeySet rks = new RowKeySet();
             Object test = coreTable.getRowKey();
             rks.getKeySet().add(coreTable.getRowKey());
             coreTable.setDisclosureState(rks);
      }If I don't set the rowKey via the setRowIndex method above, the getRowKey does not return a valid rowKey. In my case, I only want one master row to be disclosed at a time.
This all works great except for a bit of flicker to process the PPR request for the component.
Next step is to see if I can scroll the Inline Detail table to the detail row selected in the Query/Result page.
Tom

Multiple details table on the same page

Newbi to APEX. Can I have muliple details table for update/insert in tabular format on the same page with the same master? Thanks!

In the meantime, I can answer to your questions:
· Why does JHeadstart not make use of the UIX-Struts integration (see Chapter 15 of the UIX developers Guide)?This has been done to allow the same page to be run both with Struts and MVC Framework, without needing to change the page. Using the UIX-Struts integration would have made the pages 'controller aware'.
· How do you specify which columns/attributes in a Table Layout are sortable?As far as generation is concerned, you can only specify the whole table to be sortable. In case of UIX you can post-gen modify the <sortableHeader> tag of each column separately. In case of JSP you can remove the <a href> tag for each column that you do not want to sort on.
Jan Kettenis
JHeadstart Team

Master table, detail table, detail table not getting refreshed selection

i have a page where i am displaying data as master table and detail table. both table VOs are based on SQL queries which use bind variables.
i have a view link between vos of type 1:M
i created master table detail table page by dropping detail iterator from data control panel under master and selecting master table detail table
on my page i see detail table records getting populated only for first record of parent table.
on changing parent record, child table shows same records and does not refresh
i am using partial triggers on both tables to be populated on a button click as i need to pass some bind variables to VOs which are taken as input from users
how can i show corresponding rows in detail table when parent record in table changes
will i have to use table selection listener
is it possible declaratively to have master detail table view when both VOs have bind variables
jdev 11 1 1 5

these are the SQLs used
Parent SQL Based VO Query
SELECT to_char(d.status_date,'yyyymmddhh24') TIME123, count(DISTINCT d.c4)
FROM t1 d,
t2 w
WHERE w.c1 = nvl(:ou, w.c1)
AND UPPER(w.c2) = UPPER(nvl(:tt, w.c2))
AND d.c3 >= :startTime AND :startTime IS NOT NULL
AND d.c3 <= :endTime AND :endTime IS NOT NULL
AND d.c4 = w.c4
AND UPPER(d.status) = 'CLOSED'
GROUP BY to_char(status_date,'yyyymmddhh24') ORDER BY to_char(status_date,'yyyymmddhh24') DESC
Child SQL Based VO Query
SELECT w.c1,
w.c5 - w.c6 processing_time,
w.c3,
w.c6,
w.c7,
w.c8,
to_char(d.status_date,'yyyymmddhh24') TIME123 FROM t1 d,
t2 w
WHERE w.c2 = nvl(:ou, w.c2)
AND UPPER(w.c3) = UPPER(nvl(:tt, w.c3))
AND d.c4 >= :startTime AND :startTime IS NOT NULL
AND d.c4 <= :endTime AND :endTime IS NOT NULL
AND d.c1 = w.c1
AND UPPER(d.status) = 'CLOSED' ORDER BY to_char(status_date,'yyyymmddhh24') DESC
view link is based on column TIME123

Master table detail table with SQL based read only VO with bind variables

i have a page where i am displaying data as master table and detail table. both table VOs are based on SQL queries which use bind variables.
i have a view link between vos of type 1:M
i created master table detail table page by dropping detail iterator from data control panel under master and selecting master table detail table
on my page i see detail table records getting populated only for first record of parent table.
on changing parent record, child table shows same records and does not refresh
i am using partial triggers on both tables to be populated on a button click as i need to pass some bind variables to VOs which are taken as input from users
how can i show corresponding rows in detail table when parent record in table changes
is it possible declaratively to have master detail table view when both VOs have bind variables
jdev 11 1 1 5
these are the SQLs used
Parent SQL Based VO Query
SELECT to_char(d.status_date,'yyyymmddhh24') TIME123, count(DISTINCT d.c4)
FROM t1 d,
t2 w
WHERE w.c1 = nvl(:ou, w.c1)
AND UPPER(w.c2) = UPPER(nvl(:tt, w.c2))
AND d.c3 >= :startTime AND :startTime IS NOT NULL
AND d.c3 <= :endTime AND :endTime IS NOT NULL
AND d.c4 = w.c4
AND UPPER(d.status) = 'CLOSED'
GROUP BY to_char(status_date,'yyyymmddhh24') ORDER BY to_char(status_date,'yyyymmddhh24') DESC
Child SQL Based VO Query
SELECT w.c1,
w.c5 - w.c6 processing_time,
w.c3,
w.c6,
w.c7,
w.c8,
to_char(d.status_date,'yyyymmddhh24') TIME123 FROM t1 d,
t2 w
WHERE w.c2 = nvl(:ou, w.c2)
AND UPPER(w.c3) = UPPER(nvl(:tt, w.c3))
AND d.c4 >= :startTime AND :startTime IS NOT NULL
AND d.c4 <= :endTime AND :endTime IS NOT NULL
AND d.c1 = w.c1
AND UPPER(d.status) = 'CLOSED' ORDER BY to_char(status_date,'yyyymmddhh24') DESC
view link is based on column TIME123

Instead of doing the master-detail layout by dragging the details over, can you try a new page where you first drag the master VO over and then drag the detail VO over, and then set partialTrigger from the detail to point to the master?

LOV in a Table - "Not a valid Value" - Urgent

Hi All,
I have an LOV inside a Table region. The table has the Add another row button. considering the table has currently 3 rows created and the user enters a dummy value not present in the LOV in the first row and tabs out. The LOV automatically pops up without any values. The issue is when the user closes the pop-up window or clicks on its cancel button. The LOV doesn't validate the data present in the text box. If the Submit button is clicked or the save button is clicked , The framework automatically validates the data present in the text box and throws an error "Not a valid value" .
Now im not sure why but the dummy data entered in the first text box is copied to the second and third text box , and the error is displayed for all the three rows. If there is valid data present in the remaining rows it just over-writes the data with the dummy value.
I have written SOP's in the controller's Process request as well as the process form request but none of them seem to display anything.
So the framework is basically validating this before the controller is called.
Im working on a 11.5.10 instance.
Need help to know if anyone has come across such a situation before.
Thanks ,
Dean

Dean,
Seems to be a looping issue. Also you need to get the exact error row.
Thanks
--Anil

More than 5 rows in the detail table for a Master Detail Portlet

I have a Master Detail Portlet.   I originally had 5 fields in the detail portlet. I have added a column to the detail portlet and now the last column is wrapped around in the portlet. I do not see a way to force it to be on the same line as the rest of the columns for the detail table.
Do I need to just delete it and re-create the portlet?
Below is the from the browser when executing the portlet.
function show_context_help(h) { newWindow = window.open(h,"Help", "menubar=1,toolbar=1,scrollbars=1,resizable=1,width=700, height=500"); }
Master action:
[None]
Insert
Update
Delete
Carrier
Carname
Line Haul Carrier?
Detail actions
Warehouse
Carrier
Service
Ship To
Country Code
Hold for
Pickup
Service?
Associate LPN
Required?
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete
[None]
Insert
Update
Delete

Easy, The default on the detail field had the Begin on New Line flag set to on.   By unchecking it I got the desired behavior.

LOVs in Detail Table

Similar Messages

Maybe you are looking for