Business Event not updating all Lines when it has same Inventory ID

​@evangrill What are you using to mark the lines? An import scenario? Can you share the details of this since it’s not the BE that is the issue I’m sure.

​@evangrill   I think there are actually two things worth checking here:

1. Raise Event setting — "Once for All Records" fires the subscriber a single time for the whole result set. If multiple SO Lines share the same Inventory ID on an order, only one may get processed. Try switching this to "Once per Record" so the subscriber fires individually for each matching line.

2. Trigger Conditions using OR — All three conditions are joined with OR, meaning the event fires if any condition is true — not all three together. An SO Line with any Inventory ID would always qualify. You likely want these joined with AND so the event only triggers when the order is Open, the line has an item, and Mark for PO is currently false.

Also, what subscriber action are you using? That would help confirm whether the "Once per Record" change alone would solve it.

If you use @@InventoryID as the key to update each line, it will only update the first record with that inventory ID. You will need to use @@LineNbr to update all lines.

Right, assuming he’s using an import he’ll need to include LineNbr and maybe a =Every line also

​@BenjaminCrisman; ​@bwhite49; ​@Naveen Boga 

Thank you for your insights and suggestions.  Attached the import scenario that runs the Business Event.  It is an inherited one when I took on this role.  It does seem that the prior person did have the Line Number but then inactivated the record.  Also, they didn’t use the @@ wild card key to help.

Any thoughts?

1. Add the SOLine.LineNbr field to your inquiry GI640608.
2. Go to data provider screen and refresh the columns in the data provider
3. Replace the purple with @@LineNbr = [Transactions.LineNbr] (internal field)
4. replace the blue/teal with LineNbr = SOline_LineNbr

1. Add the SOLine.LineNbr field to your inquiry GI640608.
2. Go to data provider screen and refresh the columns in the data provider
3. Replace the purple with @@LineNbr = [Transactions.LineNbr] (internal field)
4. replace the blue/teal with LineNbr = SOline_LineNbr

 

 

This is exactly it -- a common mistake I see is including the data in both the custom key config as well as the second line where the data should be specified.

This is outlined in the following webinar I hosted last year for import scenarios.

I definitely recommend checking out my custom key breakdown section of this webinar -- it may help in the future!