Should we use Multithreading for CSV imports by de...
# general
m
Should we use Multithreading for CSV imports by default? Shouldn't that be checked by default?
a
you don't want to use it with transaction imports, if there are multiple lines being imported
but for things like custom records, entities, items, if i have the ability to use it (you can't if you don't have at least one suitecloud plus license), then i do
m
yea that is what I meant really
Good advice! thank you
a
no prob - i guess i can't think of a reason why you wouldn't want to enable it when doing something like creating/updating customers/vendors/items, but maybe someone will chime in w/ why that could be a bad idea
j
So my understanding is that multi-threading splits it up into multiple batches and processes them all simultaneously. If you need the import to happen in the exact order they appear on your CSV (say the third record in your CSV references the first record in your CSV) or you're very particular about internal IDs or JE numbers being in a specific order then DO NOT use multi-threading, as it will just work on whatever one in whatever chunk it can get done first. As long as you don't care about the order in which your records go in, then yes, multithread away. IME transaction imports, even multiple lines ones are fine, as long as all the lines for a single transaction are adjacent to each other (but I'm pretty sure CSV import bombs out when that's not the case even for non-multithreading)