You’ll need to read the Epicor Customization and Epicor Ice Tools Guide, do the Epicor Customization Course and a strong foundation on Epicor (the application). The rest just comes with trial and error, of course resources like this website are a great addition.
To add the tracking number from Misc Shipment screen the easiest way would be a BPM on the Update method in HDCase to lookup the Shipment Record and store the Tracking Number in a UD field.
Another option is using an FKV (Foreign Key View) which allows you to reference a Foreign Table in a Customization Keyed of an existing DataView. Both of these concepts are explained in the guides I mentioned.
Ok I got it, that’s becasue that’s not a Queryable field. I thought you had made the PackNum be the same as the call Num. Instead you are using the CallNum fields in the Shipment table…FKV’s only work with primary keys. In this case you’ll have to use the BPM option.
Or manually lookup the record in code.
I tried all manner of doing this and I don’t think HelpDesk is the right table. I would think it should be MiscShip Method Directive I would need to use as that is where the tracking number will be updated either manually or by Manifest.
In my head,
I would open Erp.MiscShip.Update
Set a condition to trigger when the tracking number changes from any to other.
Add the ‘Update Table by Query’ and ‘Invoke BO Method’.
Set up ‘Invoke BO Method’ like this:
Invoke ‘Erp.ServiceCallCenter.UpdateExt’ BO method with ‘specified parameters’.
We do something like this from Misc Shipment to DMR using the DMR number in E9. The process is a method directive on MiscShp.Update. If the callnumber is not zero and the tracking number not blank then enable a post proccessing directive that sets a HDCase UD field to the tracking number.
I tried to convert my E9 abl and do this in E10, but that was well beyond my coding for now.