I am creating a Transfer Order in NetSuite via the SOAP API and I'm managing to do so just fine, without problems. I am then passing a second SOAP API call to create an item fulfilment record, basically the 3 serial numbers I want to use to fulfill the transfer order with. When I try to create the item fulfilment record, I am immediately getting this error: "Unable to find a matching line for sublist item with key: [orderLine] and value: [1]." I am setting the orderLine vales to correspond to the same values I passed in for the lines in each item in the transfer order, ie, 1 2 3. What could be the problem please, could you guide me?

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** Based on the conversations, it seems like the issue you're encountering is related to the

orderLine

field in the item fulfillment record. This field should match the

line

field on the transfer order. If these fields do not match, you may encounter the error "Unable to find a matching line for sublist item with key: [orderLine] and value: [1]." Here are a few things you could try: 1. Ensure that the

orderLine

field in the item fulfillment record matches the

line

field in the transfer order. The

orderLine

field in the item fulfillment record should correspond to the line number of the item in the transfer order. 2. Check if there are any scripts or workflows that might be interfering with the creation of the item fulfillment record. You can temporarily disable these scripts or workflows to see if they are causing the issue. 3. If you're using a third-party integration tool like Celigo, make sure that you're correctly mapping the

orderLine

field. You can use JSON paths to map any field, for example,

item[*].orderLine

. 4. One user mentioned that they encountered a similar error when they set the item fulfillment status to "C" (for Closed). They resolved the issue by setting the status to "Shipped" instead. You might want to try this as well. Remember to test these changes in a sandbox environment first to avoid any unintended consequences in your live environment.