Can't run a Master Detail form generated by Designer2.1

I can not run a Master Detail form on some of machines if the form is generated through Designer2.1 . Same form if developed in form builder can be run.
Please Help.
My Designer version in fo is as follows
Client side version information:
Low End Generator DLL Version 2.0.19.3.0 - Production
High End Generator DLL Version 2.0.19.4.0 - Production
Module Diagram and Component Editor Version 2.0.19.3.0 - Production
MS Help Generator Version 2.0.19.3.0 - Production
Forms Menu Generator Version 5.0.19.3.0 - Production
Forms Design Capture Version 5.0.19.3.0 - Production
Forms Generator Version 5.0.19.6.0 - Production
Oracle Designer/2000 Report Design Capture Version 3.0.19.5.0 - Production
Oracle Designer/2000 Report Design Capture Version 3.0.19.5.0 - Production
Oracle Designer/2000 Report Generator Version 3.0.19.4.0 - Production
Oracle Recover Custom Code Utility for Visual Basic Version 2.0.19.3.0 - Production
Visual Basic Design Recovery Version 2.0.19.4.0 - Production
Visual Basic Generator Version 2.0.19.4.0 - Production
WebServer Generator Version 2.0.19.3.0 - Production
DWRSG20 DLL Version 2.0.19.4.0 - Production
Design Editor Guides Version 2.0.19.3.0 - Production
Dwl Logic Editor Version 2.0.19.4.0 - Production
Server Modeller (32 bit) Version 2.0.19.4.0 - Production
Generator Preferences Palette Version 2.0.19.3.0 - Production
Property Palette Version 2.0.19.3.0 - Production
Property Dialogs Version 2.0.19.5.0 - Production
Object Navigator Version 2.0.19.5.0 - Production
CW NLS Message DLL (English) Version 2.0.19.0.0 - Production
CW Common Diagrammer Dialogs Version 2.0.19.0.0 - Production ( Language Version 2.0.19.0.0)
AWRS Language Independent Strings Module Version 3.0.19.0.0 - Production
AWR Repository Services Version 3.0.19.0.0 - Production
AWRE Error Handler Version 3.0.19.0.0 - Production ( Language Version 3.0.19.0.0)
RMDG RM Diagnostics Version 3.0.19.0.0 - Production ( Language Version 3.0.19.0.0)
Repository Version 3.0.19.0.0 - Production (DLL)
CORE Version 3.5.4.0.0 - Production
NLSRTL Version 3.2.4.0.0 - Production
DBMS Version 7.3.4.0.0 - Production
Server side version information:
Oracle8 Enterprise Edition Version 8.0.3.0.0 - Production
PL/SQL Version 8.0.3.0.0 - Production
Repository Version 0.1.10.0.0 - Production
CDAPI Version 2.0.19.0.0 - Production
Oracle Designer/2000 Repository (TM) Version 7.0.3.0.0 - Production
Server Side Patches
CI0217.001
CI0217.002
CI0217.003
CI0217.004
CI0217.005
CI0217.006
CI0217.007
CI0217.008
CI0217.009
CI0217.010
CI0217.011
CI0217.012
CI0217.013
CI0217.014
CI0217.015
CI0217.016
CI0217.017
CI0217.018
CI0217.019
CI0217.020
CI0217.021
CI0217.022
CI0217.023
CI0217.024
CI0217.025
CI0217.026
CI0217.027
CI0217.028
CI0217.029
CI0217.030
CI0217.031
CI0217.032
CI0217.033
CI0217.034
CI0217.035
CI0217.036
CI0217.037
CI0217.038
CI0217.039
CI0217.040
CI0217.041
CI0217.042
CI0217.043
CI0217.044
CI0217.045
CI0217.046
CI0217.047
CI0217.048
CI0217.049
CI0217.050
CI0217.051
CI0217.052
CI0217.053
CI0217.054
CI0217.055
CI0217.056
CI0217.057
CI0217.058
CI0217.059
CI0217.060

Could you go into a little more detail on when you ran into the problem? Things like:
is it after you added a rule to the form?
is it when you first try to bring up the form in an environment where you have not used Web Form Designer previously?
is it after you added a widget to the form?
Almost certain this won't help, but here's my blog on some common things you need to be aware of before starting to use the Web Form Designer or Process Player features in 11.1.1.7: Getting Started with Oracle BPM Composer Web Forms and Process Player | AVIO Consulting

Similar Messages

Limit on number of columns details of a master detail form/report

Hi,
I understand that there is a limit to the number of columns you can have in a master detail form/report. I am on Apex 4.01 and have a detail section that shows 24 months at a time as columns with integer hours assigned each month. My master detail was working fine with as many as 24 months/columns in this detail section, but I tried to re-use months by 'recycling' months, clearing them out of values and adding the months to the end of each row but now I am getting errors even though I had more columns showing before my 'recycliing' of the columns. The error is:
"ORA-06502: PL/SQL: numeric or value error: character string buffer too small "
What I don't understand is -- why am I getting this error now when I actually had more columns in the detail section months ago, and all I am doing is 'recycling' prior columns back into the detail report, not actually adding columns.
Thanks for any insights anyone can give.
Pat

DBA tells me that we are at 9.0.2.2.14, (higher version than the one you suggested) but I still get the same error.
Thanks,
Karuna

Wizard generated Master-Detail form issues

The wizard-generated master/detail forms have several severe usability issues when the "Choose Layout" option is set to "Builder master detail with: edit detail as tabular form on same page".
Some of these issues are:
- The form has two Apply Changes buttons, one to save the master row and one to save the detail row. Users find this very confusing. If you save the master row changes, any changes to the detail rows are lost and vice versa.
- The form has two Delete buttons, one to delete the master row and one to delete the checked detail rows. Users find this confusins also. Clicking the lower delete button discards any other changes that were made.
- The Add Row button also discards any other changes that were made.
The first two issues are easily fixed. With a few simple changes to the generated page, I can make it so there is a single "Apply Changes" button that 1) saves any changes to the master row, 2) saves any changes to detail rows and 3) deletes any checked detail rows.
I cannot figure out how to solve the third issue (that the add row button discards any changes). I can make it so the "Add Row" button saves the changes, but this isn't user friendly either; I don't think any changes should be comitted unless the user specifically presses 'Apply Changes'.
So far, I thought of several ways to possibly fix this but can't get any of them to work. Some of the ideas were:
1. The 'Add Row' button could run the automatic row processing and MRU processes, but not do a commit untill/unless Apply Changes is pressed. I don't think this is feasible because http is stateless and connection pooling may be used, so we can't have a transaction that spans http requests.
2. Move the Add Row process to page rendering so that the detail table always has an empty "add row" row thereby making the Add Row button unnecessary. I tried this, but it looks like the add row process was designed to run during the page processing, not during rendering, and it fails with a divide by 0 error when it is run during page rendering.
3. Use client-side DHTML (instead of the HTML DB add row process) to add an empty row to the html table (i.e. add row button does not do a submit, it is handled entirely on the client). I tried this, but the MRU process fails because it doesn't expect the added row.
If anyone has any other ideas on how to fix this problem, they would be greatly appreciated.
HTML DB solves this problem in the SQL workshop create table wizard.
In HTML DB 1.6, the "Add Column" button does a submit but somehow saves any changes that were entered.
In HTML DB 2.0 beta, client-side DHTML is used (my approach 3 above).
Can someone from Oracle share how the HTML DB create table wizard solves this problem?

Eric,
Thanks for your feedback. Iâll add your suggestions to our list of tabular form enhancement request.
The wizard generates a regular form for the master record and a tabular form for the detail records. As you pointed out, itâs quite easy to customize this to your individual needs.
Unlike regular forms, thereâs currently no session state concept for tabular forms, so you either need to write your data to the database, or you will loose any changes if you e.g. paginate. For the same reason, the âAdd Rowâ button and the associated process is generated so that any changes are saved to the database before adding a new row. Of course the MRU process that is executed on âAdd Rowâ can be removed, if that is the preferred behavior.
A work around would be to code the DML processes for tabular forms manually, and temporary store the data in HTML DB collections to simulate a stateful behavior.
In HTML DB 2.0 we started adding DHTML features, such as the create table wizard youâre referring to. Some features, like the pull down menus, will be available to be used in your own applications. Other features, like the DHTML tabular form, wonât be available for custom applications in 2.0.
Regards,
Marc

How can I insert in the table detail of a master/detail form??

Hello, I have created a master/detail form from the assistant, and with the code generated by APEX I do not manage to insert a row in the table detail, I press the button 'Add Row' and refill information, when I press the button ' to apply changes ' me the following mistake appears:
'Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-20001: ORA-20001: Current version of data in database has changed since user initiated update process. current checksum = "C85B64D53C8D63E9D3EE83B82728DFA3", item checksum = "244B1FED90DF5CC5B0DDB6728F4D02DD"., update "CRM_ADMIN"."ASIGNACIONES_AM_CONTACTOS" set "SECUENCIA" = :b1, "CODIGO" = :b2, "NOMBRE_CLIENTE" = :b3, "NOMBRE" = :b4, "COMENTARIOS" = :b5, "CODIGO_COMERCIAL" = :b6'
How I can solve and be able to insert in the table it detail?
Thanks

Hi Law,
Text in a shape or a text box will not feature in the table of contents.
To get a colour behind your titles, type them into your document (not a shape). Format as Heading or some other paragraph style the TOC will recognise.
Select the title text and Format Panel > Text > Font > Gearwheel > Advanced Options.
Choose Character Fill Color and choose a colour from the palette (left) or colour circle (right).
Example Titles (all on the same page for a smaller screen shot).
Chapter 3 (in a coloured Text Box or Shape) does not appear in the TOC:
Hint for cheats :
To give the titles a wider Character Fill Colour, add some Tab characters before and after.
Regards,
Ian.

Oracle 10gr2 Master/detail form running very slow when you navigate to the detail record.

Hi All, I have a master detail form, running in webserver, when I navigate to the detail block, the form start buffering and buttering for about 2 min. There is a trigger when-new-record instance that is firing when you navigate to a new record : The select part of this stament is taken a long time to execute. I modified this in toad and what used to take 25 seconds to run is taken less than a second now, but the slowness still persists in the form.
for rec in (select wrrh_col
                  wpbh_col_lvd,
                   wpbh_col_doc_no
      from wh_col,
           wkpl_col,
           wh_col
     where wrrh_col_no = :block.wreh_wrrh_col_no
       and wrrh_col_no = wreh_wrrh_col_no
         and wrrh_col_no = wpbh_col_no
       and wrrh_col_proj    = wpbh_col_proj
       and wrrh_proj_no     = wpbh_proj_no) loop
   if fun_name(rec.wpbh_col_lvd) = 'Y' then
    do something,
   end if;
end loop;
The select staement that used to run for 23 seconds is running in less than one second, but the form is still running very slow when I navigate to the detail record.
Please advise.
Thanks.

Thanks Andrea for your prompt response, the problem is the select statement and like I stated, I tuned the select statement in toad and what normally takes 23 secs is taking less than 1 sec to run. If I comment out the call to the function, it is still slow. The select stament will returned null and it will still be slow. When I comment out the for loop, it run very fast. I dont know what else to do than tuned the select statement.

Can't add new detail record in Master Detail form

Hi ,
I've created a simple database application from scratch by initially selecting a Master Detail page. This generated a report page (for the parent ) and a form page (for the child ). On using the form to add a new child record the following error was generated:
Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01400: cannot insert NULL into ("STUDENT1"."DELEGATE"."DELEGATE_ID"), insert into "STUDENT1"."DELEGATE" ( "DELEGATE_ID", "CLIENT_ID", "SURNAME", "INITIALS", "SEX", "SPECIAL_NEEDS") values ( :b1, :b2, :b3, :b4, :b5, :b6)
Error Unable to process update.
The 'child' field listed in the error message is automatically hidden on the form and I had presumed that on generating this form using the wizard that I would have had an opportunity to link the delegate_id field to a trigger or a sequence as seems to happen when creating a database application scratch using other page types. I'm new to Apex so I'd be grateful if anyone could let me know as to why this default behaviour occurs,
regards,
Kevin.

I tried it for Apex 4.0.2 (my version) and 4.1 (on apex.oracle.com) and I am asked for master and detail PK generation in both versions.
What are your steps exactly in the wizard? Like this?
Create page -> Form -> Master Detail Form
Now you see a whole list of sub steps including "Primary Key Source".
Oh I see "Create Application wizard." in your post. Start with an empty application (blank page) and use the Create Page wizard instead. Maybe that's the difference.
Edited by: InoL on Nov 18, 2011 9:27 AM

Can any Oracle Forms developer show what a master-details form is?

I created a master-detail form in APEX. However, the MD form really made me laugh because I needed to SAVE the master record and the detail tabular form separately. There was one SAVE button associated with the master record and one SAVE button associated with the detail tabular form. A master-detail form should let the user to SAVE the master record and the detail tabular form together - one SAVE button saves everything. This is what we can easily do in Oracle Forms - one master and several details (tabbed). I am just frustrated with all the current thin-client technologies including JDeveloper. I cannot simply tell the users that they need to nagviate between pages many times to finish data entry. It doesn't make sense to have the user requirements to fit the current "limited" technologies.

Not quite Forms functionality but master detail is shown in the Southwind demo on htmldb.oracle.com studio link.
The details need the master id, and hence the save is done prior creating details.
Forms of course relied on top down processing such that the header would be inserted before the details would be.
I know its not exactly what your looking for but it might be the best you can get..
Daryl...
ah those are the days of forms 2.3 and what were they called exit triggers ..

Can't put Combobox in Master-Detail Form

I'm trying to create Master-Detail form with LOV's, but in both the Master and Detail selection, the Item Type LOV doesn't include combobox.
From the looking at some of the Posts, this seems to be possible.
Does anyone know what I need to do?
Thanks Larry

Hi,
This is because you do not have any LOVs defined in your application. This LOV will show the LOV types, only if the application contains any LOVs. Define a LOV and then edit the form. You will be able to see it.
Thanks,
Sharmila

Is this a bug? master rowid value lost when saving on a master/detail form

master/detail forms seem to lose the rowid after saving, if the unique identifier is set to ROWID
to reproduce the problem:
1) create a master detail form on DEPT/EMP
-- choose 'Managed by Database (ROWID)' on the 'Define Primary Key' page.
-- do not include master row navigation (but i don't think this matters)
-- choose 'Edit detail as tabular form on same page' on the 'Choose Layout' page
-- include the master report
2) on the master/detail page, change the conditional branch that returns to the master report page
-- the normal condition for this branch is request in SAVE,DELETE,CREATE
-- change it to request in DELETE,CREATE
3) run the form and save a change
-- saves fine, session shows the ROWID value is still set
4) save a second change
-- change does not save, form reverts to Create mode
this problem does not occur when using the primary key columns instead of rowid
see http://apex.oracle.com/pls/apex/f?p=60813:7 for the ROWID version
see http://apex.oracle.com/pls/apex/f?p=60813:11 for the PK column version

Hi Saverio,
Bug *13563808* has been logged to track the reported issue, and a fix will be made available in a future release. Just to clarify, this issue is only arising when the APEX-generated Master-Detail is modified post-generation, so for users who have not modified their Master-Details using ROWID to manage their DML processes, they should not experience this issue.
In relation to my workaround, my suggestion works in my test environment, which I verified before posting the initial suggestion. Please note that the 'Reset Page' process is, by default, conditional on the "Delete" button being pressed. If you have made further modifications to your Master-Detail page, then this might explain why you're seeing different behaviour to me. You might using the "Debug" option on the Developer Toolbar useful. Viewing the debug information should help you to decipher what's going on/wrong on your page. If you still can't resolve the issue, then the safest option might be to revert the page back to it's original state, meaning the user navigates back to the Report page upon submitting changes to the Master-Detail Form page.
Regards,
Hilary

Master Detail Forms with 2 composite primary keys - Is there a workaround?

Hello All,
I have been searching for a workaround to the maximum 2 part primary key restriction on the multi-row updates, and master-detail forms, and am hoping that someone can help me. I am using HTMLDB v2.0.0.00.49 with IE 6 against a 9.2 DB.
I successfully implemented the workaround of Fred Stoopendaal's (see Updata PK on HTML DB ) and it works fine for single page multi-record updateable forms, but alas I haven't been able to extend it to master detail forms (I think it is something to do with Oracle not allowing the "returning" clause on views).
Here is what I tried:
two tables, one with a 2 part composite primary key, which is the master table, and a detail table with 3 part composite primary key -
--------- BEGIN SQL ---------
create table master_table
( master_col1 number
, master_col2 number
, master_col3 varchar2(30)
, constraint master_pk primary key (master_col1,master_col2));
create table detail_table
(detail_col1 number
,detail_col2 number
,detail_col3 number
,detail_col4 varchar2(30)
, constraint detail_pk primary key(detail_col1,detail_col2,detail_col3)
, constraint master_detail_fk foreign key (detail_col1,detail_col2) references master_table(master_col1,master_col2));
create or replace view v_master_table as
select rowid mata_rowid,mata.*
from master_table mata;
create or replace view v_detail_table as
select rowid deta_rowid,
(select rowid from master_table mata where mata.master_col1 = deta.detail_col1 and mata.master_col2 = deta.detail_col2) deta_mata_rowid
, deta.*
from detail_table deta;
create or replace trigger mata_ins_upd_trg
instead of insert or update on v_master_table
referencing new as new old as old
for each row
begin
if inserting then
insert into master_table (master_col1, master_col2, master_col3)
values (:new.master_col1, :new.master_col2, :new.master_col3);
end if;
if updating then
update master_table
set master_col1 = :new.master_col1,
master_col2 = :new.master_col2,
master_col3 = :new.master_col3
where rowid = :old.mata_rowid;
end if;
end;
create or replace trigger deta_ins_upd_trg
instead of insert or update on v_detail_table
referencing new as new old as old
for each row
begin
if inserting then
insert into detail_table ( detail_col1, detail_col2, detail_col3, detail_col4)
values (:new.detail_col1, :new.detail_col2, :new.detail_col3, :new.detail_col4);
end if;
if updating then
update detail_table
set detail_col1 = :new.detail_col1,
detail_col2 = :new.detail_col2,
detail_col3 = :new.detail_col3,
detail_col4 = :new.detail_col4
where rowid = :old.deta_rowid;
end if;
end;
--------- END SQL ---------
Then I created a master-detail form in Apex on the two views, using the mata_rowid and deta_rowid as primary keys, and mata_rowid=deta_mata_rowid as the link. I realise that using a function to fetch the master rowid within the detail view query is costly, but it was my intention to modify the record fetch queries to use the real FK columns once things were up and running.
It seems to generate the pages ok, and I can insert/update master table records, but as soon as I modify records in the detail table things go a bit haywire. I can't find any documentation on how the inbuilt MRU/MRD logic works, so can't figure out the issue.
Can anyone out there tell me what the problem is with the logic above, or if they have come up with a neat solution to this annoying limitation. I know that many will say that I should modify the data model to use surrogate primary keys, but many of the uses for HTMLDB are new interfaces for old schemas, so a workaround that doesn't involve wholesale data model changes would be preferable.
Thanks in advance,
Mike Cretan

Hi, this is likely not the most elegant way...but perhaps the simplest -- and I didn't have much time to play.
I used Wizard to create two separate Master Detail forms, each with a separate detail table. Thus I ended up with four pages:
Page "A" - "Selector" page for Master (Report), with Edit link driving to Detail-1
Page "B" - Editable Master/Detail-1 page (HTML / Report)
Page "C" - "Selector" page for Master (Report), with Edit link driving to Detail-2
Page "D" - Editable Master/Detail-2 page (HTML / Report)
Then I selected the primary key column TWICE on the Report on Page A. Modified the second instance of this column to navigate to Page D (passing primary key) exactly the way the original instance of this column navigates to Page B. Then I deleted Page C.
Since you can have only one Tabular Entry form per page, this seemed the best way to drive two separate detail tables from a common interface.

Requerying on Master Detail form

Hi,
Does anyone know how to set up PL/SQL code to automatically requery on a master detail form after insert/update? For example, if I insert a record on the master part of the form, I would like that record to automatically show up after the insert/update. Also, if I insert a record on the detail part of the form, I would like that record to automatically show up after an insert/update.
Thanks,
Martin

Hi Krishnamurthy,
Thank you very much for the code. The code for the most part acts like I want it to except when I initally insert a master record. In my case, I have the form set up so you have to insert a master record before you can insert any detail records. Therefore, after the user clicks save, that master record needs to come up. The code you gave me only brings up the current master record if you are inserting detail records (which is great, that is what I want it to do). I have modified the code you gave me so when a user is just inserting the master record, the master record automaticaly comes up rather than the first record in the table. However my code makes the form run slow (about 13 seconds to save). Do you know of another way that I can make the form act like I want it to. Below is my code.
Thanks again,
Martin
declare
     l_msg                varchar2(255);
     l_key_value      number(10);
     l_key_value2      number(10);
     v_get_id           number(9);
     v_check_detail      number(9);
     CURSOR GET_ID IS
          SELECT MAX(A.PCH_ID)
          FROM PORTAL30.PCHEADER A;
     CURSOR CHECK_DETAILS IS
          SELECT DISTINCT B.PCD_ID
          FROM PORTAL30.PCDETAILS B WHERE B.PCD_PHC_ID = v_get_id;
begin
     /*get the key field value from the Master Detail form to requery the details since the form will be cleared out after update */
     l_key_value := p_session.get_value_as_NUMBER(
     p_block_name => 'MASTER_BLOCK',
     p_attribute_name => 'A_PCH_ID',
     p_index => 1
     doSave;--- This is the default handler
     OPEN get_id;
     FETCH get_id into v_get_id;
     CLOSE get_id;
     OPEN check_details;
     FETCH check_details into v_check_detail;
IF check_details%NOTFOUND
THEN
     CLOSE check_details;
     /*get the key field value from the Master Detail form to requery the details since the form will
     be cleared out after update */
     l_key_value2 := v_get_id;
     /*get the message which is going to be displayed after update */
     l_msg := p_session.get_value_as_varchar2(
     p_block_name => 'MASTER_BLOCK',
     p_attribute_name => '_STATUS');
     /*now set the key field value in the Master Detail */
     p_session.set_shadow_value(p_block_name => 'MASTER_BLOCK',
     p_attribute_name => 'A_PCH_ID',
     p_value => l_key_value2,
     p_language => PORTAL30.wwctx_api.get_nls_language);
     WWV_MASTER_GENSYS_1(p_block_name => null,
     p_object_name => null,
     p_instance => null,
     p_event_type => null,
     p_user_args => null,
     p_session => p_session);
     /*put the message(like 'Updated one master record' ) back in the screen */
     p_session.set_value(p_block_name => 'MASTER_BLOCK',
     p_attribute_name => '_STATUS',
     p_value => l_msg);
     p_session.set_value
     (p_block_name => 'MASTER_BLOCK'
     ,p_attribute_name => '_MASTER_ACTION'
     ,p_value => 'NONE');
     p_session.save_session();
ELSE
     CLOSE check_details;
     /*get the message which is going to be displayed after update*/
     l_msg := p_session.get_value_as_varchar2(
     p_block_name => 'MASTER_BLOCK',
     p_attribute_name => '_STATUS');
     /*now set the key field value in the Master Detail*/
     p_session.set_shadow_value(p_block_name => 'MASTER_BLOCK',
     p_attribute_name => 'A_PCH_ID',
     p_value => l_key_value,
     p_language => PORTAL30.wwctx_api.get_nls_language);
     WWV_MASTER_GENSYS_1(p_block_name => null,
     p_object_name => null,
     p_instance => null,
     p_event_type => null,
     p_user_args => null,
     p_session => p_session);
     /*put the message(like 'Updated one master record' ) back in the screen*/
     p_session.set_value(p_block_name => 'MASTER_BLOCK',
     p_attribute_name => '_STATUS',
     p_value => l_msg);
     p_session.save_session();
END IF;
END;

Master Detail Form - unable to add detail row

Dear,
I have a test application that runs for years on apex.oracle.com.
Since 3rd of june 2010 I am unable to add rows on a detail form.
Any ideas?
Help is welcome!
Kind regards
Lorenz

4.0 Conversion Issue
Lorenz stated I can create the orderheader, but unable to create orderlines.Simply nothing happens, when I click the add row button.>
I share the same issue as Lorenz, on a Master/Detail form, I am able to create my Master row and but nothing happens when attempting to create detail rows. I was able to switch my application to theme 13 (Traditional Blue) from 2 (Blue and Tan) and was then able to create and add details rows.
My dilemma. When switching to theme 13 and others, none appear to support Two Level Tabs in the same manner as Theme 2. Essentially the applications look and feel is not going to go over well with my user base of 3+ years.
Is there another standard theme that will support Two Level Tabs like Theme 2 and allow the addition of detail rows on a Master/Detail form?
Is this a reported 4.0 conversion issue?
Jeff

Master Detail Form - How 2 update a field in the Detail form using a query?

Hello,
I have a master detail form with, each master record having a fixed(6) number of detail records. One of the fields in the detail record is the PART_DESCRIPTION field. I am trying to update this field by querying Table_X. TABLE_X is in the format of (desciption id, description). Description id runs from 1 to 6.
When the form displays, the PART_DESCRIPTION field for the 6 detail records needs to be automatically populated with the six values of description stored in Table_X. How can this be done?
Tried using session storage objects, but made no headway.
Would greatly appreciate pointers on how to go about doing this.
Thanks.
Dev

If you are on a Portal Version lesser than 3.0.9.8.3, then please try the following to populate
the PART_DESCRIPTION field.
Steps:-
1> Edit the form and go to the Additional PL/SQl section and put the following code in the
"...after displaying the page area" :-
declare
type t_vc_arr is table of varchar2(4000) index by binary_integer;
l_arr_desc t_vc_arr;
l_form_name varchar2(200);
l_form_state varchar2(500);
begin
l_form_name := p_session.get_module().get_name();
l_form_state := p_session.get_value_as_varchar2(
p_block_name => 'MASTER_BLOCK',
p_attribute_name => '_FORM_STATE'
if l_form_state = 'QUERY_AND_SAVE' then
select description
bulk collect into l_arr_desc
from <schema>.table_x;
htp.p('
<script>
var descArr = new Array();
var Fidx = 1;
var formObj = document.WWVM'||p_session.get_id()||';
var fieldName = "'||l_form_name||'.DETAIL_BLOCK.PART_DESCRIPTION.0";
for i in 1..l_arr_desc.count loop
htp.p('descArr['||to_char(i-1)||']="'||l_arr_desc(i)||'";');
end loop;
htp.p('
for (var i=0; i < formObj.length; i++){
if (formObj.elements.name == fieldName+Fidx){
formObj.elements[i].value = descArr[Fidx-1];
++Fidx;
htp.p('</script>');
end if;
end;

Portal Master-detail form how to auto assign detail record sequence number

Portal Master-detail form how to auto assign detail record sequence number.Please help me?

You can just read the following section
Can I specify a sequence number generator as the default value for a form column?
Yes. Enter the following in the "default value" field for the column:
#<schema name>.<sequence name>.nextval
where <schema name> is the name of the schema containing the sequence, and <sequence name> is the name of the sequence. The entry is preceded by a "#".
For example, if the schema name is "SCOTT", and the sequence name is "CUSTOMER_SEQ", the default value entry is:
#SCOTT.CUSTOMER_SEQ.NEXTVAL
same way you can do for master - detail form.
for more information on forms please refer the following URL.
http://otn.oracle.com/products/iportal/htdocs/portal_faq.htm#BuildingApplications
hope it helps.

Many to many master detail form

Hi All,
APEX 3.1.2 on SuSE 10 Oracle 10.2.0.3 64 bit
I am new to APEX, but used OAS several years ago. Back then I hardcoded all htp.print commands. We are building an intra-team application to track system relationships. For example,
web interface 3 --> application server 2 --> database 6
Our tables are similar to the following
SYSTEMS
system_id (unique sequence)
system_type_id (database, app server, apache, etc.)
SYSTEM_TO_SYSTEM
publishing_system_id - number
consuming_system_id - number
We would like to have a master detail form where we would query database 6 for example, and then see all related systems one level below it (application server 2 in the example above). I have been able to query the related systems and show them in a drop down pick list on the detail form, but I cannot edit them.
The wizard asked for the primary key of the detail table, which in this case is not a sequence generated value, but a pick from a systems table lookup on system_id/system_name.
If the master form would automagically lass the system_id to the publishing_system_id on the detail form, and allow me to update that with a picked system_id tied to consuming_system_id, that would be perfect.
I can write the htp calls I mentioned earlier, but I am sure I am missing something.
Does anyone have any best practices for this?
Thanks!
Steve

Hi Steve,
Here is an example which might help you:
http://apex.oracle.com/pls/otn/f?p=43368:35
Here, I have used two tables e.g. test1 and test2. Test1 has an id column which is just a sequence column and the name column in this table has a unique key.
Table test2 has id column as primary key and name1 column is linked with Test1 table on the Form. Name2 column is not required to be linked with Test1 table.
If this is what you are after, then I can give your more detail for it.
Hope it helps.
Zahid

Can't run a Master Detail form generated by Designer2.1

Similar Messages

Maybe you are looking for