Importing row data with an auto-numbered header

@Michael Hansen , hard to say from the import scenario you shared. Everything looks good to me. The only thing I would recommend, is to apply a sort condition on the GI (not in the GI UI itself, but in the mapping here):

And there, sort by POOrder_usrContainer. Let me know if this solves the issue.

The container number is a parameter for the GI. EVERY row shown is using the same Container ID. Below is a snippet of the GI:

In that inquiry we only run it one container at a time, which is why I picked container number as the “temporary” order number. I’m starting to wonder if this is an issue with the Besiness Event and NOT an issue with the import scenario.

EDIT: Tested using your suggested method, no changes, still getting multiple SO’s of type TR generated instead of one SO of type TR. But thank you for digging!!!!

This event runs off an ACTION on the Inquiry, where I select the boxes to ACT on. Due to the way our inquiry runs, I just use “IMPORT ALL”, but I have tried it manually selecting the rows and it still gives the same output.

EDIT: You WIN! The issue was the Raise Event. I had it set to each record, but I needed it for ALL RECORDS. Below is the revised BE that is working like a dream. You are AWESOME YURI!!!