CSV import error “record has been changed” - using multi-threading

AI generated answer (using internal Slack threads):

The error "record has been changed" during a CSV import in NetSuite typically occurs when there is a conflict between the data being imported and the existing data in the system. This can happen if the record being imported has been modified in NetSuite after the CSV file was created, or if another process (like a script or a user action) is modifying the record at the same time the import is happening. When using multi-threading for CSV imports, it's important to be aware of the potential for these types of conflicts. Multi-threading splits the import into multiple batches and processes them simultaneously, which can lead to records being processed out of order. If the import needs to happen in the exact order they appear on your CSV (for example, if the third record in your CSV references the first record in your CSV), or if you're particular about internal IDs or JE numbers being in a specific order, then you should not use multi-threading. For transaction imports, it's generally recommended not to use multi-threading, especially if there are multiple lines being imported. However, for things like custom records, entities, items, multi-threading can be beneficial if you have the ability to use it (you need at least one SuiteCloud Plus license). If you're getting an error that a record does not exist during a CSV import, it could be because you're specifying an internal id for a new record. The internal or external ID is used as the reference key for an existing record, meaning they are for updates only. If you're creating a new record via CSV import, you should not specify an internal id. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******