Adf master -detail data table

Hi,
I have adf master detail data table , I put af:selectbooelancheckbox and autosubmit is true in detail data table .When I click the detail table , valuechangelistener of the af:selectbooelancheckbox is runnig I don't want this situation. Is it possible to prevent this ?
regards,

Hi
I can't remove autosutmit = true because I handle the valuechangeevent in managedbean.Why master table event fire the valuechangeevent in detail table ? I check the submit source in managedbean but It doesn't prevent to fire valuchangeevent ? Is there any way except ignore autosubmit = true ?
thx,

Similar Messages

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

ADF Master Detail Forms

Hi,
We have a master detail views and the master detail relationship is working fine between the views. We have a requirement to display one master form and 2 detail forms (user has to see two detail forms) to the user. The default master detail relationships in ADF are displaying one master form and one detail form with the navigation controls. Can you please suggest ideal approach for displaying multiple detail forms.
We tried with the af:iterator for displaying details collection model as multiple forms. But the problem with the current approach, we are unable to get the reference to the detail record when a value is changed in the detail form.
<af:iterator id="i1" varStatus="vs" value="#{bindings.BillDetailVO11.collectionModel}" var="row">
<af:inputDate id="serviceDate"
label="Service Date"
value="#{row.ServiceDate}" *valueChangeListener="#{backingbean.myvaluechangelistener}"*
columns="9"/>
<af:inputText id="it1122" label="POS"
value="#{row.PlaceServiceCode}"
columns="4"/>
</af:iterator>
I am comfortable with the iterator approach if I can get the value of PlaceServiceCode for the same row in the detail form when the ServiceDate value changes. I am ready to try for alternative approaches for displaying multiple detail forms.
Thanks and Regards,
Prasad

Hi Shay,
Thank you for responding to my query. I followed the steps in the blog and created two detail forms. But both the detail forms are representing the same detail record. Our requirement is little different.
We have to create a master detail form (Bill Summary with Bill Lines) to edit the bill summary with lines and display two Bill lines along with summary to the user.If hte number of bill lines are more than 2 then we have to display navigation controls to the user to navigate across the bill lines.
As an example the form data comes from Bill_summary(Master) and Bill_Lines (detail) tables. If the number of Bill Lines are 5 then we have to display the form as follows. if the user selects next the form should display 2,3 lines, 3,4 lines etc.
BILL_SUMMARY
BILL_LINE 1
BILL_LINE 2
<Navigation control for the details>
Thanks and Regards,
S R Prasad

ADF: Master Details Page

Hello,
I have just started out trying to develop an application in JDeveloper with ADF and I am coming from a Apex/Forms/PL SQL background. I am trying to develop an online application form for our Grants program.
The problem I am having is I have a master detail type page where I have a section D (Master) and then I have a breakdown of cost (detail). I have created a creation page for the section D and I have then another creation section on the same page for the breakdown of the costs by dragging the view that is under the section D view.
The problem is the detail section seems to be bring back the first record from the table. This is not what I expected as I would assume this to be blank record as we have a blank record in the master part.
Is there anyway around this where on startup the detail section brings up a blank record instead of the first record in the view?
Cheers in advance in any help on this matter.
Paul.

Most likely you dragged the wrong detail structure from the Data Control palette. When you created your Application Module, and added View objects to it, you would have seen a tree structure. Views will be listed separately, but if you have a View Link associating a detail view with its master, you will also see that view in the tree under the master. Something like this:
MyMasterView
MyViewLink
MyDetailView
MyDetailViewMake sure that this structure has been moved to the right side of your Application Module. There you will see something like:
MyMasterView1
MyDetailView2
MyDetailView1This is what creates the tree structure in the Data Control palette. When you created your master/detail page, you dragged MyMasterView1 for the fields from your master view. But you probably dragged MyDetailView1 for the details. This does not use the View Link to associate your details with the current master record. To do this, you must use MyDetailView2, which you will find by expanding the tree under the master.
Now, to get a blank record in the detail, you have to execute a Create action from that data control. You can drag a Create button to the page, and the user can press the button to get a blank record. Or you can cause a create action to happen whenever you enter that page.

ADF Master Detail Insertion and updation

Dear All
I am developing a web application with the ADF using ADF BC4J as a buisness service and JSP as th view.
I am creating a Master detail page that makes the user add the ,master and the detail(s) information in the same page.
Example:
you may insert the department and the employess in that department in the same transaction (post) also the update

Two questions...
1. Will a future version of Jdeveloper support a drag and drop update-able multirow table?
2. The existing example of doing this (Without Jheadstart) behaves different than a single row input form, as Duncan Mills points out, in that it loses the values that are input if validation errors occur. This same thing happends in the JHeadstart workspace.
a) after running the code and just showing the bindings and form values, it appears a standard input form has the new values immediately after processUpdateModel(). Even if they are in error, and it later fails to make it through validateModelUpdates the values are retained.
b) in the Multi-row example, you can examine the form bean values (for the multiple rows), and examine the values from the rowset obtained through the DCUtil.findSpelObject() and JUCtrlValueBindingRef calls, and the bindings don't change. The validateModelUpdates still manages to produce the error though.
So, with a multi-row update form...
a) How do you get the ROW specific error msg generated from a declarative or method-based validator? - that is, put a msg in for the row like: You can't put XXX into this field.
Right now, we modified the BEAN to include an ErrMsg column and added that as a transient attribute to entity and view, and can display the messages via that by putting them in during the processUpdateModel(). Of course, most of the validation ended up in the processUpdateModel(), with none in the Entity.
b) Where are those values going if they are placed into the bindings as they can't be examined later after processUpdateModel?
Here's a method stub that we used to show values...
   * showFormValues retrieves the array of form beans as well as the
   * EmployeesView1.rangeSet, and displays the form values for Salary
   * and CommissionPct against the JUCtrlValueBindingRef (row-based)
   * bindings from EmployeesView1
   * @param actionContext
private void showFormValues( DataActionContext actionContext )
      DynaActionForm updateForm = (DynaActionForm) actionContext.getActionForm();
      UpdateRowBean[] updatedRows = (UpdateRowBean[])updateForm.get("Row");
      System.out.println("********** showFormValues **********");
      java.util.List origRows =
        (java.util.List) DCUtil.findSpelObject(actionContext.getBindingContainer()
                                             , "EmployeesView1.rangeSet");
      // Now loop through the bean array
      for (int i = 0; i < origRows.size(); i++)
         //Get the rowKey of the submitted updated Row
         String theRowKey = updatedRows.getRowKeyStr();
//Get the corresponding row from the origional set
JUCtrlValueBindingRef oldRow = (JUCtrlValueBindingRef)origRows.get(i);
//Check the update row needs processing and matches the source row
if (oldRow.get(JUCtrlValueBindingRef.RANGESET_ROW_KEY_STR).equals(theRowKey))
// Form value - does not appear to change
System.out.print( i + ": sal=" + updatedRows[i].getSalary() +
", comm=" + updatedRows[i].getCommissionPct() );
System.out.println("....Salary=" + oldRow.get("Salary") +
", CommissionPct=" + oldRow.get("CommissionPct") );
} // match on rowKeyStr
} // for i
System.out.println("************************************");
} // showFormValues

ADF-Master detail-Foreign key generated By Trigger won't propaget to Detail

Hi All,
We have Master-Detail Table where Master table key is generated by DB.
And this key act as Foreign key in detail table.When we Creates Master Table records and commit it .It gets saved correctly But when we navigate to Create Detail record (Cretae button is taken from Detail) It opens in Create mode but does n't poppulate Foreign Key.
Can anybody plz explain..
Regards
Yogesh

Hi Frank,
Thanks for your reply.I don't know "the ADF Business Components tester "
what is this ?
I was able to solve my problem by making "Refresh after insert " Check box selected in Entity object.Now it is generating Master Key and also i am getting it in Detail.
But now problem is, Can we make details record in insert mode by 'Create opration' under Master View.My requirment is insert two records in detail table in background while inserting record in master.Where relationship is maintained by foreign key which generated by trigger.
I want master and detail create form on same page where i will make details from Rendering False i.e both should be in Create mode (Accesser should not retrive record).
In Short
ADF-BC Master Detail - Detail Record insert in Back ground on the same page
Thanks in Adv
RHY

Master/Detail data error problem -- Please Help

Hi All,
I just created a M/D form for two of my tables (Organization & Contact tables) using wizard with existing sequences to create app. Everything looks great when viewing an existing account and making modifications.
My problem stems when I try to create a new account, the Organization form comes up. After entering data and hit 'Create' I get error ORA-01403: No data found. Yet it creates account. Is there a way to get both M&D forms up at the same time with no error after entering data?????
I am too new to know what is going wrong and my manuals do not clarify anything. I'd appreciate any help from a master in Master/Detail forms. :o)
Thanks,
d.

Hi All,
Just in case anyone has same problem. Since I was not able to get help here I created a tar and we figured that the problem was with the system when I upgraded. System created triggers that were fighting with the sequences that I had manually created.
Disabled triggers and all is working fine. You still need to watch future applications just in case.
Later,
d.

Master - details data population using partial trigger

Hi,
Iam using jdeveloper 10.1.3.4.0
My requirement is I need to populate a field in master when i enter a value in detail column using partial triggers.
I have taken Employee table as master and job table as detail. In the detail table i have taken 2 columns and one transient variable column when i enter values in that 2 columns the transient column is populating value using partial triggers but it is not populating the value in the master column though i have a given a partial trigger to it.

Thanks for your response. But I dont understand your question. How to test that in Tester.
I simply did the following. I created Department as master and Employee as Details recrods. And I created ADF form for Department and Employees for ADF table. And i put autosubmit = true and valueChangelistener for the Employees Salary field in the following way.
<af:inputText value="#{row.Salary}"
required="#{bindings.DepartmentsView1EmployeesView3.attrDefs.Salary.mandatory}"
columns="#{bindings.DepartmentsView1EmployeesView3.attrHints.Salary.displayWidth}"
binding="#{backing_View.inputText14}"
id="inputText14"
autoSubmit="true"
valueChangeListener="#{backing_View.valueChange}">
And Enable the partial trigger for PhonenUmber field in Employee Records and DepartmentName in Department Master record.
<af:inputText value="#{row.PhoneNumber}" simple="true"
required="#{bindings.DepartmentsView1EmployeesView3.attrDefs.PhoneNumber.mandatory}"
columns="#{bindings.DepartmentsView1EmployeesView3.attrHints.PhoneNumber.displayWidth}"
binding="#{backing_View.inputText11}"
id="inputText11"
partialTriggers="inputText14"/>
<af:inputText value="#{bindings.DepartmentName.inputValue}"
label="#{bindings.DepartmentName.label}"
required="#{bindings.DepartmentName.mandatory}"
columns="#{bindings.DepartmentName.displayWidth}"
binding="#{backing_View.inputText5}" id="inputText5"
partialTriggers="inputText14">
And the following code is added in my BackingBean.
public void valueChange(ValueChangeEvent valueChangeEvent) {
inputText11.setSubmittedValue(null);
inputText11.setValue(inputText14.getValue());
inputText5.setSubmittedValue(null);
inputText5.setValue(inputText14.getValue());
My phone number field in the Multirecord block that is Details record is shown the value, But single record block that is Department's Department Name field is not shown the Value.
Kindly let me know if i did any mistakes.
Thanks

Summary Report using Master-Detail Data on Siebel BI Publisher Report

I have to create a Summary Report using Master-Detail relationship. Report fields are Account Name, Special Need Type, Customer Status, No of Customers, No of Claims. I am using rtf to create template and any help is highly appreciated
<?xml version="1.0" encoding="UTF-8" ?>
- <ListofIO>
- <ListOfBipCustomerSpecialNeeds>
- <Account>
<Name>CVNE</Name>
- <ListOfContact>
- <Contact>
<SpecialNeedsFlg>Y</SpecialNeedsFlg>
<SpecialNeedsType>Large Text</SpecialNeedsType>
<PersonUId>1-6NI9</PersonUId>
- <ListOfContact_Claims>
- <Contact_Claims>
<AccountNumber>TEST0015362272</AccountNumber>
<ClaimNumber>1-4FVL</ClaimNumber>
<ClaimStatus>Closed</ClaimStatus>
<ClaimGBPAmount />
</Contact_Claims>
</ListOfContact_Claims>
</Contact>
- <Contact>
<SpecialNeedsFlg>Y</SpecialNeedsFlg>
<SpecialNeedsType>Braille</SpecialNeedsType>
<PersonUId>1-L0A</PersonUId>
- <ListOfContact_Claims>
- <Contact_Claims>
<AccountNumber />
<ClaimNumber>1-ACX6</ClaimNumber>
<ClaimStatus>Open</ClaimStatus>
<ClaimGBPAmount>818.18196694218</ClaimGBPAmount>
</Contact_Claims>
- <Contact_Claims>
<AccountNumber />
<ClaimNumber>1-GI58</ClaimNumber>
<ClaimStatus />
<ClaimGBPAmount>45454.099173473</ClaimGBPAmount>
</Contact_Claims>
</ListOfContact_Claims>
</Contact>
- <Contact>
<SpecialNeedsFlg>Y</SpecialNeedsFlg>
<SpecialNeedsType>Large Text</SpecialNeedsType>
<PersonUId>1-6FPP</PersonUId>
- <ListOfContact_Claims>
- <Contact_Claims>
<AccountNumber>CVNE</AccountNumber>
<ClaimNumber>1-7BRL</ClaimNumber>
<ClaimStatus>Reviewed</ClaimStatus>
<ClaimGBPAmount>562</ClaimGBPAmount>
</Contact_Claims>
</ListOfContact_Claims>
</Contact>
</ListOfContact>
</Account>
<Login>SADMIN</Login>
</ListOfBipCustomerSpecialNeeds>
</ListofIO>
Edited by: user2298324 on 13-Aug-2010 09:36

Thanks for the reply. The many to many relationship between Claims and Payments are achieved through intersection table in siebel. When Customer has multiple claims, single payment issued for both claims. Also single claim can multiple payments such (part compensation, interests, final compensation etc)

How to build a screen with master detail data

Hi ,expert ,
Someone can teach me how to build a screen with master detail table ?
I wnat to build a screen for user to maintain FERT group and FERT detail list in one screen .
just like this ..
MASTER Block
FERT1
FERT2
FERT3
DETAIL Block
FERT1A1
FERT1A2
FERT1A3
when I double click FERT1 in the Master Block the detail view will show FERT1A1 A2 A3
Thanks for your help ....
Moderator message : Not enough research before posting. Spec dumping not allowed. Thread locked.
Edited by: Vinod Kumar on Jun 13, 2011 1:38 PM

An inefficient way to create the array is to use the build array and a shift register as shown below. It's more effecient in terms of memory management to create the array and then use the replace array subset as shown in the other image. Of course, if you don't need the array inside the loop, just wire the value out of the while loop and on the exit tunnel, right click and select 'Enable Indexing'.
Message Edited by Dennis Knutson on 07-03-2007 10:25 PM
Message Edited by Dennis Knutson on 07-03-2007 10:26 PM
Attachments:
Crude Build Array.PNG ‏4 KB
Better Build Array.PNG ‏6 KB

2 different master/detail data sets

Hello. I have created a master/detail dataset for a photo gallery, with customised css. Whenever I tried to use this same spry tool for different purposes, so with different customised css, the photo gallery data set was roped into the new layout. To make the two independent, I tried saving the master/detail css of the photo gallery to an external style sheet - not sure why (I'm new to this), thought it would detach those rules from the default settings. Now when I add a new data set it appears with no css attributes at all. Help much appreciated.

I understand completely the desire to do something that turns out to be really complicated! But therein lies a real goal.
Have you uploaded this to a server, so I can see your code in action (or frozen...as the case may be!)?
To target specific IDs:
Wrap the entire masterdetail widget in a div:
<div id="galleryone">
<div class="MasterDetail">
        <div spry:region="ds1" class="MasterContainer">
          <div class="MasterColumn" spry:repeat="ds1" spry:setrow="ds1" spry:hover="MasterColumnHover" spry:select="MasterColumnSelected">{thumbnail}</div>
        </div>
        <div spry:detailregion="ds1" class="DetailContainer">
          <div class="DetailColumn">
            <h2>{title}</h2>
          </div>
          <div style="position: relative;"><div class="DetailColumn">{image}
          <div class="DetailColumn credit">{credit}</div></div></div>
          <div class="DetailColumn top"><em>{medium}</em>   {size}</div>
          <div class="DetailColumn">{date}</div>
          <div class="DetailColumn">{place}</div>
          <div class="DetailColumn">{price}</div>
          <div class="DetailColumn" id="sold">{sold}</div>
        </div>
        <br style="clear:both" />
      </div>
</div>
Then you can restyle the CSS file by making a complete copy of the CSS file and re-linking it:
@charset "UTF-8";
/* SpryMasterDetail.css */
/* Copyright (c) 2007. Adobe Systems Incorporated. All rights reserved. */
/* This is the selector for the main Master/Detail structure container.
* If you want to constrain the width of the Master/Detail structure, set a width on
* the Master/Detail container. By default, our structure expands horizontally to fill
* up available space.
#galleryone .MasterDetail {
    font: 100% Verdana, Geneva, sans-serif;
    margin: 2px;
/* This is the selector for the Master Container element which houses all the MasterColumn
* classes. By default the Master column occupy about 35% from the width of the
* entire structure.
#galleryone .MasterDetail .MasterContainer {
    width: 99px;
    float: left;
    height: 650px;
    overflow-y: auto;
/* This is the selector for a Master Column element which holds the actual data for
* a master column.
#galleryone .MasterDetail .MasterColumn {
    font-size: 75%;
    padding:5px 10px 5px 0;
    cursor:pointer;
    float: left;
/* This is the selector for a highlighted Master Column element.
#galleryone .MasterDetail .MasterColumnHover {
    background-color: #090;
/* This is the selector for a selected Master Column element.
#galleryone .MasterDetail .MasterColumnSelected {
    padding: 25px 5px;
    color: black;
/* This is the selector for the Detail Container element which houses all the DetailColumn
* classes. By default the Detail column occupy about 60% from the width of the
* entire structure.
#galleryone .MasterDetail .DetailContainer {
    padding:10px 0 0 0;
    width: 605px;
    float: right;
    overflow: auto;
#galleryone .DetailColumn.position {
    position: relative;
/* This is the selector for a Detail Column element which holds the actual data for
* a detail column.
#galleryone .MasterDetail .DetailColumn {
    margin-bottom: 1px;
Notice that I have pre-pended the #galleryone to every style in this stylesheet. Be sure to leave a space after #galleryone. This focuses specifically on the master/detail in <div id="galleryone">. Make sure this file is loaded after any generic master/detail CSS file. Better yet, make all your galleries specific with IDs (both in the page and in a CSS file).
If I only have small changes to make, I would add the additional styles into the generic stylesheet:
.MasterDetail {
    font: 100% Verdana, Geneva, sans-serif;
    margin: 2px;
#galleryone .MasterDetail {margin: 30px;}
Note that I only made a style selector for the one attribute that changed. All the other attributes will remain the same (font: 100% Verdana, Geneva, sans-serif;)
It is possible that styling other than specifically master/detail styling will vary from gallery to gallery.
For instance, if h2 will change from gallery to gallery:
#galleryone h2 {color: red;}
Do this in either your general or your master/detail stylesheet.
Curly brackets are the two keys to the right of the "P" key on the keyboard...shift to get curly brackets.
When you make a secondary stylesheet (named to correspond to its use), you must attach it to your page using the Link icon at the bottom of the CSS Styles Panel. Browse to the file and press the Link radio button. Then your additional styles will show in your stylesheet.
Beth

ADF Master Detail entry form issue

Hi All,
I am new to JDeveloper and I am creating a Master Detail entry form. I have separate buttons to create master records and detail records in Master and Detail sections respectively. After completing data entry in Master portion, when I hit the create button to create a line in detail, it removes data from the last field of master which is a "description" field. I haven't write any custom code yet. How can I fix this?
Help will be appreciated.
Thanks,
CAH

Hi,
Thanks for your reply and links to the tutorials.
I have changed the default binding to CreateInsert from Create. Unlike in the sample application in the links, my form is editable at both the levels. Apart from the clearing out the description field, it clears out the list items I have defined at Detail level when I create second or greater record. It works fine for the first record at Detail level. And as I mentioned, I have not written any custom code anywhere.
Any clue will be a great help.
Thanks,
CAH

Adf Master-detail relationship

As per my requirement i have to use master-detail in my application.....
but we can drag as master-detail relation from Datacontrol palette .....but i don't want inbuilt function ......i want create same master detail relation ship programmatically .....
Thanks in advance

Hi Frank,
I have created master and detail within one form and one submit action to save the master and detail values in the form.Example: i am using oracle schema. i have used DEPT table and EMP table.
<af:form>
Master DEPT:
DEPTNO -- input value
DEPTNAME -- input value
Detail EMP:
EMPNO-inputvalue
EMPNAME-inputvalue
DEPTNO-input value (i[b] dragged the detail table and i included with in form, when i am running the page i am getting this detail dept no textfield prepopulated as deptno 20)
</af:form>
<commit button>(commit for entire master and detail. Need to save the master and detail after user filled the form)
Please guide me or help or provide solution to solve the problem.
Thanks & Regards
Arun

Adf Master Detail disclosed

I have a master detail table and i want to my table, when page loads, all nodes come expanded. How can i do this?
Sorry about my english and thanks.

Hi,
in a managed bean, create a JSf reference to the table. Then use
public void setTable(CoreTable table) {
RowKeySet rks = new RowKeySet(true);
table.setDisclosureState(rks);
this.table = table;
Frank

ADF Master Detail Insert Page

Hi all,
i must create a jsp with a master detail in insert mode. The problem is that the master and the detail must be validated in the same time because i must have a record in the master that must have NECESSARILY a record in the detail.
All the samples that i've been found makes validate first the master and then the detail...can anyone help me?
Thanks in advance...
Fabio

you make both insert, whitout any automatic validation...then, in the onCommit metod manually check your conditions, and eventually you force rollback: what about this solution?

Adf master -detail data table

Similar Messages

Maybe you are looking for