It allows you to work with related records as if they were subrecords. For example, you open an Invoice and start a transaction so that changes to line items can be rolled back if the Invoice is cancelled (something that automatically happened with subrecords). But then you want to drill down to another table related to Invoices and have those changes treated independently of the whether or not you cancel the Invoice. This is also how it worked with subrecords and was actually a very important feature of subrecords—that they were considered part the parent record and not independent; like structured data within a field.
------------------------------------------------ Richard Wright DataDomain [email protected] ------------------------------------------------ > Date: Mon, 27 Aug 2018 13:08:32 -0700 > From: Kirk Brooks <[email protected]> > > Hey guys - the very issue with the record counter is sketched out in the > discussion about Suspending Transactions: > > http://doc.4d.com/4Dv16/4D/16.3/Suspending-transactions.300-3652126.en.html > > > I had missed this - it's quite a feature. > > On Mon, Aug 27, 2018 at 7:54 AM Keisuke Miyako via 4D_Tech < > [email protected]> wrote: > >> transactions can be paused since v16 >> > > -- > Kirk Brooks > San Francisco, CA > ======================= ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
