DevForce Community Forum : How do others handle detail lines? http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce 2010 : How do others handle detail lines? Sat, 11 Apr 2026 16:48:34 -700 Tue, 19 Oct 2010 09:51:40 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=2225 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ How do others handle detail lines? : #2 without hesitation. Invoice... http://www.ideablade.com/forum/forum_posts.asp?TID=2225&PID=8820#8820 Author: midnit
Subject: 2225
Posted: 19-Oct-2010 at 9:51am

#2 without hesitation.
 
Invoice basically having its own ViewModel when 'Add Detail' is commanded we InvoiceDetail.Create(Invoice) which returns the new InvoiceDetail which goes into the VM's InvoiceDetails Collection. Throw in some housekeeping code. Very desirable options. As in canceling the InvoiceDetail, not the Invoice, or rolling back to various states of the InvoiceDetail.
]]> Tue, 19 Oct 2010 09:51:40 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2225&PID=8820#8820 How do others handle detail lines? : I have been debating this for... http://www.ideablade.com/forum/forum_posts.asp?TID=2225&PID=8780#8780 Author: BillG
Subject: 2225
Posted: 13-Oct-2010 at 11:29am

I have been debating this for a while now and would like to hear how others handle this situation. You have 2 classes, Invoice and InvoiceDetail. Invoice is the parent and InvoiceDetail is the child. The user creates a new invoice by clicking a button so you call Invoice.Create() and it creates a new invoice object in memory. They add a detail line by clicking add on a grid.  Which of the following do you use or is there another I am missing?
 
#1 - Create an InvoiceDetail object by calling InvoiceDetail.Create which creates an object in memory and link the child to the parent. Call Save on the step. The problem is if the user cancels the whole invoice, then you have to remove that object.
 
#2 -  Create an InvoiceDetail object by calling InvoiceDetail.Create which creates an object in memory and link the child to the parent. Do not save the detail line but add it to a ObservableCollection of Invoice Details. When the invoice is saved, the Invoice parent and the list of children are saved to the appropriate tables. If the invoice is cancelled, then the Invoice object is cancelled and the ObservableCollection children are removed from memory and the list is destroyed.
 
I used to do #1 but I am beginning to do #2 now for new projects. Any thoughts out there?
 
Bill
]]> Wed, 13 Oct 2010 11:29:17 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2225&PID=8780#8780