On Fri, Apr 1, 2011 at 17:03, Paul McNett <[email protected]> wrote: > On 4/1/11 12:56 PM, Nate Lowrie wrote: > > I have a bizobj for an addresses table. The addresses are tied to > > customers, orders, and some other places in the system. The business > > requirement is that we persist old address data for customers so that > > the addresses tied to orders don't change. When a user edits an > > address, if there are any changes, I need to be able to make a copy of > > the data as a new record with the is_active field set to true and then > > revert the old record and set it's is_active field to false. I would > > like to define this at the bizobj level and I think it should go after > > validation but before the save completes. > > > > Does this sound reasonable and if so, would any of y'all have a code > > snippet for something like this? > > I've always handled this by having address fields at the order level, that > get copied > from the customer record when the order is created...
I don't really have this option because I am interfacing with a legacy system that operates in the above manner. Regards, Nate --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
