Hey Admins! Any tips for speeding up imports? We are going live on Sept 5th and doing some load testing in Sandbox. Long story short...Custom Records FLY! Customers, Vendors, Projects are Mediocre. Transactions take FOREVER! Looking at our volume and current sandbox performance, we wont be able to process all transactions for all subsidiaries by Monday morning (even if we start on cut off EOB Thursday and start loading Friday AM).

Do you have Multi-Threading as an option on the second screen (where you select Add/Edit/Upsert)? I can't remember what licensing you need to have that, but that helps a bunch. If you don't, I'm not sure there are a lot of options other than trying to add that on quick. I'm not sure NS would be able to turn it around that fast and I know "pay NetSuite more" isn't a great option. Note that Sandbox is going to be slower than Prod, so the metrics you're coming up with won't necessarily apply to Prod.

Thanks for the reply. No go on that multithreading. Assuming that is suitecloud plus.

Are you transactions large in number of lines? I know in the UI, performance starts to drag a bunch if you get into transactions with hundreds or thousands of lines. It takes forever to do anything. That really shouldn't be an issue on CSV I wouldn't think, but you could try breaking the transactions into smaller pieces.

Yeah. the pattern we are trying tonight is loading all of the transaction headers. Then queuing up all the transaction line imports to run over night. For some reason we keep getting logged out (even though we changed to 720 minutes). Wish imports wouldnt stop if user gets logged out 🙁

Make sure that Run Server Side scripts and workflows are not checked on the saved CSV import.

is loading all of the transaction headers. Then queuing up all the transaction line imports to run over night.

Wait are you saving like the header + 1 line initially and then editing the transaction each time you add additional lines? So for a ten line transaction you're technically touching the transaction 9 times? That could be part of your performance issue if so. You'd probably want to group the data together for each transaction using External ID so it shoves the whole transaction in at once. Or is that what you started doing and that was too slow? Also, I didn't think the user logging out should stop the import. Are you using the base CSV integration functionality or some other tool like NetSuite integrator or a 3rd party tool?

Funny. I was literally on the phone with NetSuite about this yesterday. I started a case as our CSV import speed dropped MASSIVELY after the OCI database migration. We can only import about 100 records per minute. But I have a catalog of 50k items where I need to make changes to thousands frequently. To update 12k records takes two hours, where it used to take maybe 40 minutes. I have a support case that I am fighting to escalate. After 7 years of "expected" CSB speeds, I find it unacceptable that they are essentially "throttling" that import speed to a crawl. I am trying the suggestion to disable "Run Server Side Scripts" to see if that will help, but I do think that regardless of workflow/scripts, them migrating to a slower data environment (to save themselves money, I assume?) is pretty bogus. So I'm making a fuss, and think others should as well.

Multi threading is part of SuiteCloud Plus. I would recommend it for large immigration imports. https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N347015.html

@Dan Curtis agreed. We disabled all workflows and SS scripts. To update 1 picklist field on 22,450 Sales Orders it took 2 hours, 19 minutes. To do that same think in our SQL database (legacy system) it took 1 minute, 8 seconds.

Do imports really stop if you log out? I've never heard that one before.

Yep. 100%

Literally never ever ever ever seen CSV imports stopping upon logout. I have CSV imported 1M rows over 5 threads, backlogged by 10 CSVs on each thread. If you are seeing this, you have other issues.

I was going to say the same thing about never needing to log out... But wasn't sure if it's related to service tier. We are enterprise

That would be kind of messed up if you have to pay extra to not have imports fail when you log out. Especially when there's no restart logic. Seems like there might be issues with that account.

they dont fail

Did the rest of the records fail? and if so, what was the error?

no. nothing failed. It just pauses the import process.

Time to open a ticket my guy.