Editing "Master Detail" Details during Create Application

I have been using the wizard to create an application.
I have added a Master Detail page, I wanted to change the page name of "Master Detail" to something more meaningful.
I clicked on the Page Name and in the pop-up window I edited the page name.
On clicking 'Apply Changes' I get the following error: "Error in mru internal routine: ORA-20001: no data found in tabular form"
This appears to only happen for Master Detail pages as I can make changes to other pages.
Regards,
Jon

Hi Jon,
Thanks for reporting this issue. I've been able to reproduce this behaviour on apex.oracle.com. Bug *10202722* has been logged to track this issue. We'll endeavour to resolve this issue in our next release. In the meantime, as you know, you'll be able to modify the 'Master Detail' page name post-generation. Sorry for any inconvenience, but thanks again for reporting this.
Regards,
Hilary

Similar Messages

Sample code to edit master detail records

Hi,
Could anybody please sned me the sample code to edit master and detail records.
Thanks,
Kavitha

Arjuna,
Thanks for your reply. Unfortunately the 'switcher' code which makes an attribute editable, works on a 'Read-Only table' page but not on 'Master-Detail table' page. The switcher code is:
<switcher childName="${uix.current.RowID.inputValue == bindings.RowID.inputValue ? 'selected' : 'notselected'}">
<case name="selected">
<textInput model="${bindings.RequestedBudget}" columns="14" readOnly="false"/>
</case>
<case name="notselected">
<textInput model="${uix.current.RequestedBudget}" columns="10" readOnly="true"/>
</case>
</switcher>
We do have individual bindings for all table attributes. Any suggestions will be much appreciated.
Thanks, Ali.

Master Detail page. - Create Row.

Hi
I have created a master details search page using the following BC4J objects
EmployeeEO - empId,name,deptno
DepartmentEO - deptno,deptname
EmpToDeptAO - using deptno
EmployeeVO - contains all Attributes of EmployeeEO
DepartmentVO -contaiins all Attribute of DepartmentEO
EmployeeAM contains both VO
The search page is working fine.
In the Search page i have created a create button.When this click this button will be forwarded to create page.
In the create page under the pagelayout region i have two table regions
one Employee Details Entry and the second one deparment details entry.
i have added apply button to the page.
in Process request of controller i have invoked the two create(insert row) methods (one for employeeVO and another for departmentVO)which resides in AM.
in process form request when apply button is pressed, i will commit the details.
Employee details getting committed but department details is not getting committed.Its throwing some exception like the Fonreign Key constraint violated.
but if i give some department no which is already existing in department table region both is getting committed.
How to handle this problem.
how to issue commit separately for master and detail.
Am i clear with the explanation.
Edited by: user10613877 on Dec 13, 2008 9:04 AM

I guess you will also need a View Link between the the 2 VOs.
Also the attributes that would be used to join, should be declared as Key Attributes. Here in your case, Dept_Id should be the key Attribute in both the VOs.
You can refer this link.
[master-detail mandatory steps|http://apps2fusion.com/at/ps/333-oa-framework-master-detail-region-mandatory-steps]

Example of how to create a master-mutiple detail BI Publisher 10.1 Report

Hi,
Are there any examples out there on how to do this? Basically for each master record from table A,
need multiple related detail records from table B AND multiple related detail records from table C.
Ie. A is master to B AND A is master to C.
For master-single detail reports, writing a single query that joins master to detail works fine,
but for master-multiple detail reports, I don't see how this approach will work.
Thanks,
Jed

Sure, here is one (hand edited, but shows some structure).
Detail rowset2 relates to rowset1 via STDINV_ID.
Detail rowset3 related to rowset1 via STUDY_ID and STDINV_ID.
Thanks for your consideration.
-Jed
<?xml version="1.0" encoding="UTF-8"?>
<DATA>
<ROWSET1>
<ROWSET1_ROW>
<STUDY_ID>105</STUDY_ID>
<STUDYNAME>TEST293</STUDYNAME>
<INVNAME>Flinstone, Fred</INVNAME>
<COUNTRY>USA</COUNTRY>
<STDINV_ID>3721</STDINV_ID>
<ROWSET2>
<ROWSET2_ROW>
<STDINV_ID>3721</STDINV_ID>
<TEMPLATESENT>11/02/2006</TEMPLATESENT>
<FINALCONTRACTRECEIVED>11/13/2006</FINALCONTRACTRECEIVED>
<CONTRACTTYPE>Main Agreement</CONTRACTTYPE>
<DRAFTRECEIVED></DRAFTRECEIVED>
<EFFECTIVEDATE>11/13/2006</EFFECTIVEDATE>
<EXPIRATIONDATE></EXPIRATIONDATE>
<CONTRACTSTATUS>Executed</CONTRACTSTATUS>
</ROWSET2_ROW>
</ROWSET2>
</ROWSET1_ROW>
<ROWSET1_ROW>
<STUDY_ID>105</STUDY_ID>
<STUDYNAME>TEST293</STUDYNAME>
<INVNAME>Bell, Taco</INVNAME>
<COUNTRY>USA</COUNTRY>
<STDINV_ID>3157</STDINV_ID>
<ROWSET2>
<ROWSET2_ROW>
<STDINV_ID>3157</STDINV_ID>
<TEMPLATESENT>07/12/2005</TEMPLATESENT>
<FINALCONTRACTRECEIVED></FINALCONTRACTRECEIVED>
<CONTRACTTYPE>Main Agreement</CONTRACTTYPE>
<DRAFTRECEIVED></DRAFTRECEIVED>
<EFFECTIVEDATE>04/05/2006</EFFECTIVEDATE>
<EXPIRATIONDATE></EXPIRATIONDATE>
<CONTRACTSTATUS>Executed</CONTRACTSTATUS>
</ROWSET2_ROW>
</ROWSET2>
<ROWSET3>
<ROWSET3_ROW>
<STUDY_ID>105</STUDY_ID>
<STDINV_ID>3157</STDINV_ID>
<EXPIRATION>10/02/2007</EXPIRATION>
<IRBNAME>Big Kahuna IRB</IRBNAME>
</ROWSET3_ROW>
<ROWSET3>
</ROWSET1_ROW>
<ROWSET1_ROW>
<STUDY_ID>105</STUDY_ID>
<STUDYNAME>TEST293</STUDYNAME>
<INVNAME>King, Burger</INVNAME>
<COUNTRY>USA</COUNTRY>
<STDINV_ID>3112</STDINV_ID>
<ROWSET2>
<ROWSET2_ROW>
<STDINV_ID>3112</STDINV_ID>
<TEMPLATESENT>07/10/2005</TEMPLATESENT>
<FINALCONTRACTRECEIVED>11/21/2005</FINALCONTRACTRECEIVED>
<CONTRACTTYPE>Main Agreement</CONTRACTTYPE>
<DRAFTRECEIVED></DRAFTRECEIVED>
<EFFECTIVEDATE>11/23/2005</EFFECTIVEDATE>
<EXPIRATIONDATE></EXPIRATIONDATE>
<CONTRACTSTATUS>Executed</CONTRACTSTATUS>
</ROWSET2_ROW>
<ROWSET2_ROW>
<STDINV_ID>3112</STDINV_ID>
<TEMPLATESENT></TEMPLATESENT>
<FINALCONTRACTRECEIVED></FINALCONTRACTRECEIVED>
<CONTRACTTYPE>Amendment 1</CONTRACTTYPE>
<DRAFTRECEIVED></DRAFTRECEIVED>
<EFFECTIVEDATE>04/01/2008</EFFECTIVEDATE>
<EXPIRATIONDATE></EXPIRATIONDATE>
<CONTRACTSTATUS>Executed</CONTRACTSTATUS>
</ROWSET2_ROW>
</ROWSET2>
<ROWSET3>
<ROWSET3_ROW>
<STUDY_ID>105</STUDY_ID>
<STDINV_ID>3112</STDINV_ID>
<EXPIRATION>08/16/2011</EXPIRATION>
<IRBNAME>Top Notch Healthcare</IRBNAME>
</ROWSET3_ROW>
</ROWSET3>
</ROWSET1_ROW>
</ROWSET1>
</DATA>

I created an allowance for my daughter but can't get past the edit Apple ID details. I get Your information could not be saved at this time.

I had to create an account for her because she is underage but I can't get past the edit Apple ID details page. I have confirmed the email address and was able to set up some of the services on the iPod but can't finish setting up the account.

I'm experiencing the very same thing. I assumed that the site was down, but it looks like there are multitudes of complaints about this. What's up Apple? I can't seem to find an answer to this online... Thanks!

How to create one Oprations button (Create Button Or CreateInsert Button )for all master And Detail block?

hi
I have master And Detail with 4 level ,I want to have on operations button for all block in data control .
(similar to Oracle form toolbar)
how to do it ?

Well, if you tell us your jdev version and what exactly you try to do, without just telling us 'as in forms' we might be able to help.
Most of us don't know how it's done in forms. So be specific when you describe your use case.
Timo

Example of how to create a master-multiple detail PDF report using BI Pub

Hi,
Are there any examples out there on how to do this? Basically for each master record from table A,
need multiple related detail records from table B AND multiple related detail records from table C.
Ie. A is master to B and A is master to C.
For master-single detail reports, writing a single query that joins master to detail works fine,
but for master-multiple detail reports, I don't see how this approach will work.
Thanks,
Jed

You MIGHT have a better response if you ask this question in the BI Publisher forum...: BI Publisher
Thank you,
Tony Miller
Webster, TX
There are two kinds of pedestrians -- the quick and the dead.

Master form -detail table

Hi,
Jdeveloper Verison: 11.1.2.1.0
I m creating a master detail form .
hr_feedback_mt
id_feedback
employee_no
id_training_program
trainer
location
attended date
hr_ratings_tt
id_feedback
id_question
rating
hr_questions_mt
id_question
question
I have created master EO and VO for hr_feedback_mt, hr_ratings_tt. created associations and viewlink between EO and VO's.
On the form I have dragged the master VO from the data control as form, and detial VO as editable table.
On master from i clicked createinsert operation and filled the attributes. on details table, i click on createinsert operation, it creates on row in the detail table.
But actually when i click on createinsert operation of detail table, i need to display all the questions(rows and the ratings so that user fills all the questions.
on commit master and detail should be saved into the database.
How to achieve detail table to show all the questions on one click of createinsert operation and user fills all the questions and ratings.

There is no automatic insert of all possible question in the detail table. You have to do this by hand in a beam method or better in a service method in the Application module or VO.
Timo

Post-generating 3-level master-detail-detail screens

Hi all,
for a consulting project, I had to create several three-level master-detail screens using JHeadstart. For the JHS demo app, this would mean for example that a location page contained a list of departments at the location and underneath it a list of employees working at the currently selected department.
From what I have learned so far using JHS, this is not supported by the wizards and should be done by post-generation changes. This forum has a few topics mentioning the problem and possible solutions, but most of the time just fragments of the complete solution/approach. As I had to create several of these 3-level detail screens, I tried to uniformly document them, providing the 7-step guide as outlined below. I only started working with JHS recently, so please let me know where I take a long way round or where my approach is not appropriate at all :o)
NOTE1: Terminology-wise, for the example given above, I will call the departments the 2nd level detail and employees the 3rd level detail, while locations are the first level masters. I hope this is not too confusing ;o)
NOTE2: the example code is not guaranteed to work with the JHSdemo. I just changed the names of variables and classes from my own application to the familiar entities of the demo.
STEP 1: Generate plain MD screens for the first and second level entities (table-form) using the JHS application generator and make sure all generated features you want in your page are OK. Afterwards, switch off the UIX generation in your application structure file. If you want multiple entities at the third detail level,
STEP 2: Add the functional contents of the generated 3rd level detail UIX page to the main master UIX page, right underneath the 2nd level detail-table but still inside the <header> entity of this 2nd level detail. (I'm not too sure whether this really matters, but at least the indentation looks nice). What I call "functional contents" is the <header> entity containing the 3rd level detail table.
STEP 3: Edit the java file of the 3rd level view object, adding a variable storing the identifier (primary key) of the currently selected 2nd level detail row. If you haven't used the java file before, generate it by doubleclicking the view object and checking the generate view object box in the Java screen.
private String $selectedDeptID;
public void setSelectedDeptID(String id) {
$selectedDeptID = id;
STEP 4: Edit the java file of your application module (in the model layer) and add a method for updating the view objects search queries like the example below:
public void updateEmployeeView(String deptID) {
// fetch the view object instance
EmployeeViewImpl view = (EmployeeViewImpl)this.getEmployeeView1();
// register the currently selected departments ID
view.setSelectedDeptID(deptID);
// re-execute the view objects query
view.executeQuery();
// reset the selected ID
view.setSelectedDeptID(null);
STEP 5: Create a java class for handling the event when a user selects a different 2nd level detail row.
package view;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpSession;
import oracle.adf.controller.struts.actions.DataActionContext;
import oracle.adf.model.BindingContext;
import oracle.adf.model.bc4j.DCJboDataControl;
import oracle.adf.model.binding.DCDataControl;
import oracle.adf.model.binding.DCUtil;
import oracle.cabo.servlet.BajaContext;
import oracle.cabo.servlet.Page;
import oracle.cabo.servlet.event.EventResult;
import oracle.cabo.servlet.event.PageEvent;
import oracle.cabo.servlet.ui.data.PageEventFlattenedDataSet;
import oracle.cabo.ui.data.DataObject;
import oracle.cabo.ui.data.DataSet;
import oracle.cabo.ui.beans.table.SelectionUtils;
import oracle.jbo.ApplicationModule;
* USER-DEFINED EVENT-HANDLING CLASS
* this class is triggered after the user selects another row in the Department
* table/form in the Locations.uix screen. It derives the ID (pk) of the
* selected row and launches the AppModule method to update the view objects
* select queries with the selected DeptID.
public class RowSelector
* private variable holding the name of the DataControl module for this
* Application Module
private static final String DATACONTROLNAME = "AppModule" + "DataControl";
* private variable holding the name of the table/form object in the uix page
* from which we want to derive the selected row data.
private static final String TABLEFORMNAME = "DepartmentsView2";
* private variable holding the name of the form field holding the database
* ID (pk) of a row in the ${TABLEFORMNAME} table/form
private static final String IDFIELDNAME = "Dept_ID";
* This method fetches the ID of the user-selected row in the DepartmentsView2
* table/form in the Locations.uix form.
* Afterwards, it fires the ApplicationModule method for updating the view objects
public static EventResult doSelectionEvent(BajaContext bc, Page page, PageEvent event)
try {
// create a new FlattenedDataSet for the table name
DataSet tableInputs = new PageEventFlattenedDataSet(event, TABLEFORMNAME);
// fetch the UI table index from the DataSet (NOT the pk from the db)
int index = SelectionUtils.getSelectedIndex(tableInputs);
// fetch the DataObject representing all the input elements on the current table row.
DataObject row = tableInputs.getItem(index);
// fetch the value of the input field holding the ID (pk) of the selected department row
Object value = row.selectValue(null, IDFIELDNAME);
if (value != null) {
// tell the AppModule to update the appropriate view object(s)
getAppModuleImpl(bc.getServletRequest()).updateEmployeeView(value);
// quick and dirty exception handling. not too many exceptions possible due to
// hard-coded field/table/module names. anyway, taking no action at all is not
// that bad an option for a demo ;o)
} catch (Exception e)
e.printStackTrace();
return null;
* method for fetching the active Application Module
public static AppModuleImpl getAppModuleImpl(HttpServletRequest request)
BindingContext ctx = DCUtil.getBindingContext(request);
DCDataControl dc = ctx.findDataControl(DATACONTROLNAME);
AppModuleImpl service = (AppModuleImpl)dc.getDataProvider();
return service;
STEP 6: Override the executeQueryForCollection method in your view object java file to make sure it uses the selected 2nd level detail rows ID for the bound variable specifying the 3rd level select query. Otherwise, the select query for the 3rd level detail set appears to use the ID of the first 2nd level detail row selected for the currently selected 1st level master. In the example below, no other bound variables are used in the view object, otherwise, the indexing might have to be adjusted.
protected void executeQueryForCollection(Object qc, Object params[], int noUserParams) {
if ($selectedDeptID != null) params[0] = $uur;
super.executeQueryForCollection(qc, params, noUserParams);
STEP 7: In the Locations.uix page, set a primaryClientAction for the radio select input in the 2nd level detail screen. This action should fire an event (fe 'userChoseDepartment') and refresh the 3rd level detail tables using the partial refresh options in the primaryClientAction dialog window. Afterwards, add an event handler to the bottom of your Locations.uix page, linking the event specified before to the doSelectionEvent in the RowSelector class.
So, that's how it worked for me. I hope it does the same for you and please do post any comments or remarks if problems arise or simplifications are possible. The more remarks or bugs appear in the above code, the more the JHS team is hinted to enable auto-generated 3rd level detail screens :-D
Cheers,
benjamin

Benjamin,
Thank you for sharing your expreinces with us!
A few remarks:
1. With JHeadstart 10.1.2.1 you can generate unlimited master-detail levels in the same page when using UIX and table-layout for the detail groups This feature is implemented usin g UIX table detail disclosure: when you click on the "show" link in a row in of the level 2 detail table, you will see in the detail disclosure area the level 3 detail table.
There is a screen shot of this feature in the JHeadstart Developers Guide for 10.1.2.1, chapter 3, section "Creating Table Pages". You can now download the dev guide from the JHeadstart Product Center:
http://www.oracle.com/technology/consulting/9iservices/jheadstart.html
2. You have a lot of steps related to synchronizing the level 3 ViewObject with the level 2 ViewObject. You can leave all this work to ADF Business Components, by adding the l;evel 3 ViewObject as a nested usage to the level 2 ViewObject in your application module data model.
Ths would save you the work you aredoing in steps 3 to 6.
Steven Davelaar,
JHeadstart Team.

Pagination for Master Form, Detail Table

Hi,
I am using JDev11.1.2.1.0
I am creating a page having master detail relationship (master as a form and detail as a table). On click of First, Prev, Next, Last pagination button of master should change the data and refresh child table data.
So created a Master VO & Child VO joined with View Link and dragged into page as Master form, Detail table. But during pagination, NEXT works once, then it seems to stop there. LAST works and FIRST & PREVIOUS seem to both go to the first record.
Can anyone suggest me when I went wrong.

Yes Frank, its st. forward use case. I tired with master table with detail table works fine but master form with details table behaviors differently.
Below snippet of code in JSPX page master form detail table as shown below :
<af:panelFormLayout id="pfl6">
<af:panelLabelAndMessage label="Name:" id="plam1">
<af:outputText value="#{bindings.EMP_NAME.inputValue}" id="ot2"/>
</af:panelLabelAndMessage>
<af:panelGroupLayout id="pgl15" layout="horizontal">
<af:commandButton text="First"
disabled="#{!bindings.First.enabled}"
partialSubmit="true" id="cb1"
actionListener="#{bindings.First.execute}"/>
<af:commandButton text="Previous"
disabled="#{!bindings.Previous.enabled}"
partialSubmit="true" id="cb2"
actionListener="#{bindings.Previous.execute}"/>
<af:commandButton text="Next"
disabled="#{!bindings.Next.enabled}"
partialSubmit="true" id="cb3"
actionListener="#{bindings.Next.execute}"/>
<af:commandButton text="Last"
disabled="#{!bindings.Last.enabled}"
partialSubmit="true" id="cb4"
actionListener="#{bindings.Last.execute}"/>
</af:panelGroupLayout>
</af:panelFormLayout>
<af:table rows="#{bindings.EmpSchemesViewObj1.rangeSize}"
fetchSize="#{bindings.EmpSchemesViewObj1.rangeSize}"
emptyText="#{bindings.EmpSchemesViewObj1.viewable ? 'No data to display.' : 'Access Denied.'}"
var="row" styleClass="AFStretchWidth" autoHeightRows="5"
columnStretching="column:c2"
value="#{bindings.EmpSchemesViewObj1.collectionModel}"
rowBandingInterval="0" contentDelivery="immediate"
selectedRowKeys="#{bindings.EmpSchemesViewObj1.collectionModel.selectedRow}"
selectionListener="#{bindings.EmpSchemesViewObj1.collectionModel.makeCurrent}"
rowSelection="single" id="t1"
partialTriggers="::cb1 ::cb2 ::cb3 ::cb4">
<af:column headerText="#{msg.LONG_NM}"
sortProperty="#{bindings.EmpSchemesViewObj1.hints.REGISTERED_NAME.name}"
sortable="false" id="c1">
<af:outputText value="#{row.REGISTERED_NAME}" id="ot9"/>
</af:column>
</af:table>
Edited by: 879073 on Jan 22, 2013 3:36 AM

Master/Detail/Detail form... Help

I know there are some entries in the forum about this but I tried some of those with no results.. I also found some demos in apex.oracle.com but since I cannot edit the code I cannot find the answer myself...
The steps I am using are these:
1. Created a master/detail form using he wizard... (Master/Detail1)
2. Create a new region in the form for detail/detail (lets call it Detail2) of type Updateable Report. This report will select form a table with 2 columns ( LinktoDetail1Id, myValue)
3. Create item P_mycolumnvalue in region Detail2 that is populated when a row in Detail1 region is selected
4. Edit the propertied for Detail2 -> LinktoDetailId column, in the item properties I Enter Default type: Item (Application or page item name) in Default value I entered P_mycolumnvalue item ..
When running it I get this error:
ORA-01790: expression must have same datatype as corresponding expression
Can anyone explain in detail how to link Detail1 with Detail 2 for when inserting data?
thanks

I think the problem is in the way I defined the Item to store the ID from Detail1.. so Let me rephrase my question...
I need a master/detail1/detail2 form to insert data...
I am trying to use
How can I (link) assign the ID from Region Detail1 into a column in region Detail2. I assume by using default field .. but I get the error I mentioned above when doing it

Help! Master-Detail-Detail problem!

Dear all,
I am using Jdev.10.1.3, ADF + BC.
I have 3 tables: table1(Master), table2(Detail, foreign key set, reference to tabel1) and table3(Detail, foreign key set, reference to table2).
I created an edit form by the following steps:
1) Selected table1 from the Data Control Palette --> Forms --> ADF Form....
2) Selected table3 from the Data Control Palette --> Master-Details --> ADF Master Table, Detail Table
3) Delete the "Submit" button in Master Table
4) Change the "Submit" button to "Delete" (with backing bean) in Detail Table
5) Added 3 buttons (with backing bean) at the bottom of the form (i.e. Save, Delete, Cancel)
6) There is a menu at the top of the form
7) e.g. there are 2 records in Master table and each record contains 3 Detail records
The data retrieve is no problem.
When I clicked the radio button for the first record in the Master table, and then click the Save/Delete button at the bottom of the form. No problem.
However, when I clicked the radio button for the second record in the Master table, and then click the buttons at the bottom of the form.
Duplicate Menu was displayed. Sometimes duplicate buttons were displayed. And the button didn't go to the backing bean.
I don't know why and how to solve the problem??
Hope someone can help me.
Thanks for any suggestion.
Regards.

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.

Trying to edit newly inserted detail record

Hello,
I'm using Jdev 3.2. I have a JSP which successfully submits the insertion of a new master (job) record, and then successfully inserts a detail (jrefs) record using a view link.
I then want to go to a new JSP and edit the newly inserted detail record. The way my pages are at the moment, I always get the first detail record in the table, but I need to access the newly inserted one. I've messed around a bit with trying to pass the ROWKEY or retrieve the primary key from the master - but I'm just not getting it. Please can someone tell me how to set the current record to be the new detail record when I use EditCurrentRecord with the detail record view in the second JSP.
Here's some code from the first JSP, which successfully inserts the master and detail records:
<jsp:useBean id="RowEditor" class="oracle.jbo.html.databeans.EditCurrentRecord" scope="request">
<%
     RowEditor.initialize(application, session , request, response, out, "JtrackJSPSPRJjpr_jtrackpkg_JtrackpkgModule.JtjobsView1");
     RowEditor.execute();
%>
</jsp:useBean>
<html>
<head>
<%
// this is submitting the master row
Row row = RowEditor.getRowSet().getCurrentRow();
String wprov = (String) session.getAttribute("WPROV");
row.setAttribute("WpCode",wprov);
String sprov = (String) row.getAttribute("SpCode");
// the incremental part of the job number is temporarily
// stored in task_status by the business components
String jobcode = wprov + sprov + row.getAttribute("TaskStatus");
row.setAttribute("JobCode",jobcode);
// get the view link to Jtjrefs and create a linked record
ApplicationModule appModule = RowEditor.getRowSet().getApplicationModule();
ViewLink vl = appModule.findViewLink("JobJrefViewLink");
ViewObject voMaster = vl.getSource();
ViewObject voDetail = vl.getDestination();
Row newRow = voDetail.createRow();
voDetail.insertRow(newRow);
RowEditor.getRowSet().getApplicationModule().getTransaction().commit();
%>
<META HTTP-EQUIV="refresh" CONTENT="1; URL=JobRefAdd.jsp">
</head>
<body>
Here is the code from the second JSP which needs to edit the new row (newRow)
<jsp:useBean class="oracle.jbo.html.databeans.RowsetNavigator" id="rsn" scope="request" >
<%
     rsn.setReleaseApplicationResources(false);
     rsn.initialize(pageContext,"JtrackJSPSPRJjpr_jtrackpkg_JtrackpkgModule.JtjrefsView");
     rsn.render();
%>
</jsp:useBean>
<jsp:useBean id="RowEditor" class="oracle.jbo.html.databeans.EditCurrentRecord" scope="request">
<%
     RowEditor.initialize(application, session , request, response, out, "JtrackJSPSPRJjpr_jtrackpkg_JtrackpkgModule.JtjrefsView");
Row row = RowEditor.getRowSet().getCurrentRow();
RowEditor.setUseRoundedCorners(true);
     RowEditor.setTargetUrl("JobRefSubmit.jsp");
RowEditor.setDisplayAttributes("Ref1,Ref2");
RowEditor.getFieldRenderer("Ref1").setPromptText("Job Ref 1");
RowEditor.getFieldRenderer("Ref2").setPromptText("Job Ref 2");
     RowEditor.setReleaseApplicationResources(true);
     RowEditor.render();
%>
</jsp:useBean>
</body>
</html>
Any assistance would be gratefully received...

if you want to see the info that is on the track then look to the top right of the window and there is a button you can drag up and down and it closes or expandes the information so you can see if it is recording in stereo or not.
It looks like a marker pointing to the left with lines running parellel.
-Frisco

Master/detail/detail

using jsf/adf bc. I've got a jspx which needs to display data from a master/detail/detail setup. In a 'create' mode, i'm programmatically handling the create/insert stuff for the new master and detail rows. I'll try to explain my problem using a Departments/Employees/EmployeeAddresses example.
I've created a view link between Departments and Employees. I've created a view link between Employees and EmployeeAddresses. These have all been added to the active data model so that it looks like this:
DepartmentView
-Employees via Employees1
-EmployeeAddresses via EmployeeAddresses1
The code i use to create/insert the master and subsequent detail rows is as follows:
//create master (department) row
ViewObjectImpl vo = getDepartmentView();
Row departmentRow = vo.createRow();
vo.insertRow(departmentRow);
//create the detail (Employees) row to be associated with its master (Department)
ViewObjectImpl employeesVO = getEmployees();
Row newEmployeeRow = employeesVO.createRow();
employeesVO.insertRow(newEmployeeRow);
//create the detail/detail (EmployeeAddresses) row to be associated with its master (Employees)
ViewObjectImpl employeeAddressVO = getEmployeeAddresses();
Row newEmployeeAddressRow = employeeAddressVO.createRow();
employeeAddressVO.insertRow(newEmployeeAddressRow);
The problem seems to be with the last level detail row, the one for EmployeeAddresses. creating in this fashion doesn't seem to associate the new EmployeeAddress row to it's master, Employees. Although when the page is rendered, i can see that new rows have indeed been created/inserted for each of these view objects. After filling in valid values and committing, i get the JBO-27014 (Attribute is required) error for each attribute in the EmployeeAddresses table. So, it's as if this EmployeeAddress row that was created is not tied in with the Employees row, which is in turn tied in to the Department row.
Note: if i remove the create/insert code for this last detail row (EmployeeAddress) and simply have a basic master/detail setup between Department and Employee, everything works great when i create new rows this way and save. It seems that my problem stems from the fact that i'm adding another detail level onto my master/detail setup. Is there something different i should be doing?

Hi,
Thanks guys for your response.. i did it myself following way..
created 2 view links. having same source.
added both vos to same source in application module it self.
Regards,
Santosh.

Insert master, then details

I'm using JDeveloper 10.1.3.5. I've set up ADF BC EO's and VO's for a master table and a detail table. There is also a 1:* Association, and a 1:* View Link between the master and details and this has all been added to an Application Module. The primary key of the master table is a surrogate PK generated from a sequence in a trigger. So the PK attribute has been designated as a DBSequence and has Refresh after Insert turned on.
I have a jspx page using ADF Faces. It has a Create Form based on the master table. That means that a Create action was added to the page definition, and an invokeAction set to make sure Create is done when the page is first displayed. I added an InputFile component set to an UploadedFile in a backing bean. The files that users will be uploading contain detail records to be associated with this master. So I added an Iterator, Create action named CreateDetail, and AttributeValues for each attribute in the detail table's VO to the page definition. There is also a Commit action in the page definition.
In the backing bean, there is an ActionEvent method tied to a commandButton on the page. It takes the uploaded file and executes CreateDetail for each record in the uploaded file, parses the record and sets the attributes. Then it executes Commit.
Here's the problem:
If I execute Commit before I start creating the detail records from the uploaded file, then Commit again after creating details, this works fine. However, if there is an error when I process the details, the master has already been committed. I'd rather consider master and details as a single transaction to be committed or rolled back as a unit.
If I don't commit before I start creating the detail records, the new primary key for the master record hasn't been retrieved yet. So the detail records don't have the foreign key that points to the master. So the commit fails - missing mandatory field.
I tried changing the Create on the master record to a CreateInsert, hoping that the framework would do the Insert of the master and retrieve its PK before processing the details, but no dice - it still works only if I Commit before processing details.
Any ideas?

In 11g, I've had some issues with compositions automatically maintaining foreign-key relationships for a sequence-based PK correctly if both master and detail are new. Have you tried implementing the (Java) solution provided by the aforementioned section of the dev guide (even though you shouldn't need it for compositions)?
If that doesn't work for you, I've found the "old" method to be successful:
In master:
public void postChanges(TransactionEvent e) {
/* Only references if this is NEW */
RowSet newDetailsBeforePost = null;
if (getPostState() == STATUS_NEW) {
// Store the rowset of details related
// to this new image before calling super
newDetailsBeforePost = (RowSet)getXXX(); // replace "getXXX" with your association accessor method
super.postChanges(e);
if (newDetailsBeforePost != null) {
adjustDetails(newDetailsBeforePost);
private void adjustDetails(RowSet details) {
Number newFkValue = getYYY.getSequenceNumber(); // replace "getYYY" with the getter for your sequence-based PK attribute
while (details.hasNext()) {
DetailImpl detail= (DetailImpl) details.next(); // replace "DetailImpl" with your detail EO class
detail.setZZZ(newFkValue); // replace "setZZZ" with the setter for the detail's FK attribute
In detail:
public void postChanges(TransactionEvent e) {
MasterImpl master = getMaster(); // replace "MasterImpl" with master EO class, "getMaster" with assoc accessor method
if (STATUS_NEW == master.getPostState()) {
master.postChanges(e);
super.postChanges(e);
Even better is to create an EO framework class that just fixes this problem (in general) for you, but that's more complicated--<plug>see the forthcoming JDev11g handbook</plug>.
Hope this helps,
Avrom

Editing "Master Detail" Details during Create Application

Similar Messages

Maybe you are looking for