I moved the Validate 1 set of brackets up
I’m going to look at my other customizations as well . With my luck there is a DD that is overwriting the update…. If it’s actually updating
I was thinking about @jtownsend’s comment and thought this would actually be quite simple in a wizard. I don’t have your field, so I used PriorPartNum, but in trans you already have the PartNum and just need to set your field inbound.
I’ll try this but I want to change the UD field for every record in SNTran that matches the SerialNumber currently being added. I think this would only change the row being written not the historical rows in SNTran.
So when SerialNo writes a new record of PartNum: 00010 it then goes to write the corresponding transaction in SNTran for the same PartNum: 00010. At this point I want to look at all SNTran records for any part with the same SerialNumber . From there see if the SNTrranUDPart is = “0” . If so change all of the SNTran records with same SerialNumer to have that UDPart = PartNum that was written on the new record. In the screen shot those 5 previous written records of a Different PartNum would have their UDPart set to “00010” but the PartNum in SerialNo and SNTran would remain “0”
Ideally I was hoping to achieve this off the PostProcess Erp.InventoryQtyAdj.SetInventoryQtyAdj. This gives me a hook on the Select SerialNumbers and also allows as the SNtran/SerialNo DD to fire.
I think you will need to split this into two transactions. After the first save then another transaction scope to update the existing SNTrans records and I would go with @jtownsend john’s suggestion of using UpdateExt for those.
1 Like