Updating performance best practices

There’s a lot of factors at play here, so YMMV. NetSuite always says things take about 1 second per record/line for CSV imports. It’s usually it’s about 2-3 times faster than that, but the slow end estimate would put you at 21 hours, just for some reference. However, my guess would be that you have a bunch of custom stuff slowing things down if it’s really taking more than 24 hours to update 77k records. Scripts or workflows are the most likely culprit, so if there isn’t a definite need to run them for this update, try unchecking the “Run Server Suitescript and Trigger Workflows” checkbox in the Import Options (second screen) under the Advanced Options triangle-dropdown thingy.  If that doesn’t work, you’re probably going to need to take a deeper look at what’s going on with this record, and you’ll likely want to open a case with support to see if they can help. Frankly even if my suggestion helps, it’s probably worth opening a case, as sometimes there’s stuff they can do at the database level to help certain things move a little faster. I wouldn’t count on it, but worth a shot.

csv and mass update are painfully slow when you’ve got scripts/workflows firing on every row, so james’ suggestion to disable “run server suitescript and trigger workflows” is a good first sanity check. if you actually need the linked record create/delete logic, pushing it into a map/reduce and controlling exactly what loads/saves happen is usually the only way to get 77k done in a reasonable window. i had a similar import crawl while i had random junk tabs open, including https://playjackpotfishing.com/ and https://color-games.com/ and https://tongitsgogame.com/ which didn’t help my focus but the real bottleneck was still the triggered automation. also worth checking execution logs for any user event that does searches inside loops or loads related records repeatedly.