Hello all, I assume a "JE" is a Journal Entry and in modern accounting practices it is typical that a single "Transaction" has at least 2 JE's. What I'm not sure about is why the JE's are required to be created before the Transaction. This sounds like a case where you want to use a database transaction to guarantee that either all the JE's and the accounting Transaction are all created or not (i.e. no orphan objects persisted in the database). In which case I'd make the Transaction first and add the JE's either one at a time or as a list, but don't commit the database transaction until the Transaction object is populated.
HTH, Nathan ----- "dusty" <[EMAIL PROTECTED]> wrote: > Yeah Derek, we are not sure what a JE is, and transaction can mean a > number > of things. Can you post your model code and describe what you are > trying > to do in a little more detail? > > > > Derek Broughton-2 wrote: > > > > I am soooo frustrated. > > > > I have an accounting app, where accounts have JEs, and multiple JEs > belong > > to a transaction. So when I create a JE, there may not yet be a > > transaction. I can't figure out any (clean) way to make that > parent > > record. What's the proper procedure? > > -- > > derek > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/How-to-create-parent-objects--tp16377511s2369p16398229.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
