Would someone like to give an generic explanation of using the builder and any "Gotcha's" when developing BizObj forms with One to Many and One to Many to Many relationships? I have built all of my views as single table with a single bizobj per view.... but am wondering if I need a separate bizobj for a child that is also a parent (ie Parent - Child - Grandchild relationship) and it gets worse! -- I also need forms showing 4 and 5 level relationships.... Tips would be greatly appreciated!
Thanks!
<i><font color="#663300">I have many times read on this forum the 'rule of thumb' which states, "...only one updateable table per view and only one updateable view per business object. I thought I understood this axiom until tonights musings. How does one handle an update that involves child records. For instance, if one creates a new invoice it is necessary to update both the invoice table and the invoice item table. Assuming that the data entry for the invoice and items is handled on the same form, does one place two business objects on the form?</font></i>
Lynette
ltillner (AT) yahoo D.O.T com
©2001 Lynette Tillner |
