Ben_1984 Green Ribbon

Looks like adding the Line ID and setting to to null is working for us too! Thanks @Elychelle Gulen-Oracle (again, apologies for not reading your initial reply close enough).

Hi @Nicole Mendoza-Oracle, yup! Appreciate the reply and the assistance. I will be interested to see if other members pop in with any insights based on their experience, but you've given me some good references to continue troubleshooting on my end.

Thanks @Nicole Mendoza-Oracle, really appreciate the reply. The errors I'm getting will sometimes reference one script and the other times reference the other script, so probably no workflow in this case (but, I didn't even think about conflicts between workflows and scripts, so it's good to be aware of that as a…

Hello @Elychelle Gulen-Oracle my apologies! I read your initial response too quickly and didn't register that you were saying to include the line ID but set it to null. "In the Field Mapping of CSV Import, add Line ID (Purchase Order Items : Line ID) and click the pencil icon along it then select Null." I've updated my…

Hello @Elychelle Gulen-Oracle I appreciate the help troubleshooting this issue. I realize your suggesting to test with just a few lines, but I'd like to clarify how this would end up working for the full files: What I'm understanding is that I would take every line number on my existing PO and put it in my CSV with…

Hi @Elychelle Gulen-Oracle I appreciate the follow up! All of the transaction records I'm updating have multiple lines being updated (usually a couple hundred lines each, on average). EDIT FOR CLARITY — I'm not updating the individual lines for any of the transactions, I'm overwriting the full sublist for all the…

@Elychelle Gulen-Oracle appreciate the reply! Not sure if this addresses the issue for a couple reasons: 1] I am using the "overwrite sublist" option, so I would assume it shouldn't matter (just for the sake of troubleshooting, I just checked the failed transaction and each item is only listed once). I should have…

Looks like this is just a consequence of how things are designed. Got the following replies: —— "NetSuite has carefully reviewed the information on the issue and we have concluded that the behaviour is working as expected. We are reviewing SuiteAnswers to ensure that this is documented." —— Good day. We received an update…

FYI, got this update from support, "please be informed that the case is being reviewed for possible defect filing."

@Patrick Fresnosa-Oracle thanks for the follow up. I've created a Support Case. The way the documentation reads, I would expect to be able to add and update multiple transactions at the same time, . Appreciate the independent confirmation and assistance.

Hi @Patrick Fresnosa-Oracle Yup, two separate imports works (just adds an extra step for our weekly operations). When creating only the new transactions via import, I'm selecting "add" for the data handling (I haven't tried "add or update" with a CSV that only has new transactions in it, not sure if the issue would arise…

Thanks John and Patrick, I appreciate the attention to this question, and it's useful to see independent confirmation of the issue. That's an interesting idea respecting the external IDs, but, unfortunately, for us the purchase orders being updated do not have external IDs. Full context: Each week we are using NetSuite's…