Depending on the nature of the data, you could perhaps use the table field as your temporary storage (I.e. Set field local action to place your various values into the currently selected row in the table) and do a table walk to send the table values back to the actual child entry's records when you hit save on the parent. Michael.
------Original Message------ From: Brien Dieterle Sender: Action Request System discussion list(ARSList) To: [email protected] ReplyTo: [email protected] Sent: Feb 6, 2009 3:34 PM Subject: transaction for parent/child changes ** We've designed a form that has child requests displayed in a table list field. You can interact with these child requests through this form and update them via display only fields and push-fields activelink buttons etc. So the problem is you can update some things on the main form, and update some children requests, close the main request and say "yes, lose changes". A user might expect that the changes to the children would be reverted back to what they were. Is there any way to encapsulate the whole process of editing the primary requests and N children requests into a single transaction that gets committed only upon saving of the primary request? Thanks! Brien Dieterle __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___
