The Lines property is only available on Header Class objects, like SO_Invoice_Bus. 

Table event scripts apply to that specific table and oBusObj contains the handle to that specific class object.

So if you put the script on the pre-write of the SO_InvoiceTracking table, then oBusObj already refers to that table.

If you were to move your script to the pre-write of SO_InvoiceHeader then oBusObj refers to SO_Invoice_Bus and oBusObj.Lines refers to SO_InvoiceDetail_Bus. At the moment, i'm not aware of an object property that is exposed that allows you to get the object handle to SO_InvoiceTracking_Bus from SO_Invoice_Bus so you may need to get you own handle using GetObject and then loop make sure you set the browse filter for the current invoice and then loop through the records.

Thanks for that explanation, I'll have to test where I can capture all of the tracking #s for each invoice. It appears that attaching to SO_InvoiceTracking pre-write that package is already set so the handle is to a single record

KPRIMARY: InvoiceNo+PackageNo

I wonder if in scripting I can get a handle to all tracking entries for a particular InvoiceNo and loop through them. 

Thanks for the help -Ken

Refer to my last paragraph from my last post.

You will however need to set the browse filter for the current invoice number so while looping, you only see records related to the current invoice.

You can search on here for more examples of SetBrowseFilter and can also review this page for more info on the method.

http://help-sage100.na.sage.com/2019/FLOR/#Object_Reference/BaseSystem/SY_Service.htm

Thanks David, that's helpful, I hadn't thought of that method, still learning the ropes

One thing about creating a new object... you will only be able to see data that has previously been saved.  New data (new record / changes in memory only) will be inaccessible.

One thing about creating a new object... you will only be able to see data that has previously been saved.  New data (new record / changes in memory only) will be inaccessible.

Good point Kevin, unless you can find a property that will give you the object handle for the records in memory, you might have to move your script to a post-white event instead and if need be, use SetKey to get back to the invoice, I haven't had to do much with post-white events so I'm not sure if the business object and its Lines object are still technically on the same record as the one that was just written.

Great point. I'll see what works and report back for future reference.

Thanks guys