1. File size

One of the most common CSV import errors is that the file is simply too large. That can be caused by too many fields or records in the file, too many columns, or too many rows. The import error can be caused by limits set by the program using the file or the amount of available memory on the system. If your import fails because of file size issues, you need to go back and break the file up into smaller files which will enable it to successfully upload. 

2. Matching

Another key import error that pops up when uploading a CSV file is related to matching. This could be columns that don’t match expected field names caused by different values than expected, field names not on the first line, or simply the complete absence of column names.

A matching error could also occur when the expected columns are in the wrong order or required fields – columns – are missing.

3. Translation (data)

A data translation error could occur if the encoding is incorrect or unexpected. Another cause could be the presence of non-standard characters that aren’t usable. For example, it may be necessary to save a file with UTF-8 encoding in order for that file to work properly within a company’s platform. Attempting to import data with different encoded files would simply not work.

4. Values

Issues with data values can be a significant cause of CSV importing errors. These include unexpected data length – either too long or too short. It could also mean unacceptable characters such as text in a numbers-only column or numbers in a boolean (a boolean is a data type with two possible values: true or false.)

Related fields that have conflicting data such as records having multiple types of unique identifiers when only one is allowed will cause errors. For example, the city/state names are different from their actual zip code, or even a related field that does not have required data.

5. Missing data

Missing data is one of the most common errors for CSV imports. Examples include incomplete data that can be fixed by a user such as invoices that have month and day, but no year information. Other incomplete data can be addressed by a user with help from the system they’re working in. Missing city/state data with zip codes present and existing contact role information can usually be automatically appended. New contact role information including suggestions from the systems based on matching related contacts or data must be manually corrected in the system.

In some cases, incomplete data must be pulled in by a person or another system. For example, real estate sales data that is missing the original list date or comparable property information could be pulled in from public records. 

6. Non-digestible formats

Non-digestible formats include simple format mismatches that need format normalizations such as phone numbers or social security numbers which are numbers only without symbols. Complex format mismatches would need format normalization and data normalization such as when the date format is different than expected, inconsistent, or includes text rather than being normalized, for example, “July 31^st, 2020” or “Jun twentieth 19.”

Minimizing CSV import errors can be a time-consuming, laborious process, but there’s a better way: leveraging an out-of-the-box CSV data import solution can eliminate these common errors and streamline the import process. 

7. Invalid Locale Reference Key XX

The error occurs when:

1. The Multi-Language feature is enabled, and
2. You are creating an inventory item, and
3. The CSV file contains the following columns:
   1. Item Name
   1. Purchase Tax Code
   1. Sales Tax Code
   1. Quantity On Hand
   1. Price
   1. Price Level
   1. Location
   1. Translation Language
   1. Translation Display Name

To resolve this error, first, import the item without the translation, and then update the imported items with the translation data.
 

8. Please select member items before submitting

When member items are created in a separate CSV file, there needs to be a linking column: Assembly Item: External ID, Internal ID, or Name.

When performing the import, ensure that the following options are specified:

• Import Type – enter Item
• Record Type – enter Assembly/BOM Item
• Click Multiple Files to Upload
  • For Primary File – Item, select the file with the Assembly Item
  • For Linked File (Optional) – Item Members, select the file with member items
• Data Handling – click Add
• Map all Assembly Item fields with fields from the Item folder
• Map the Member Items name and quantity with Item (Req) and Quantity in the Item Members folder.

9. Invalid price level reference key XXX

When importing, an invalid price level reference key error will occur.

To resolve this error:

1. Go to Setup > Accounting > Setup Tasks > Accounting Lists.
2. Set Type to Price Level.
3. Make sure that the Price Level set in the CSV file is:
   1. Not set to Inactive
   1. Correctly spelled

10. Could not find any records by this name

The error occurs when updating child matrix items.

In the CSV file, enter a separate column for the parent matrix item and another for the child matrix item. The CSV file will look like the following:

Item Name/Number	Subitem of	Department
Child item	Parent item	—

The previous example assumes that the Department field is being updated on the Child Matrix Item record.

Also, in the Item Name/Number column, the Parent: Child format should not be used. The Child Matrix Item Name is entered without the Parent Matrix Item name. For example, use Basket rather than Containers: Basket.

You can also use the internal ID of the child matrix item.

Go to Home > Set Preferences > General. In the Defaults field group, check the Show Internal Ids box to show the internal id on a list.

11. Invalid asset account reference key xxx or Invalid cogs account reference key xxx

The error occurs when updating the asset or COGS account on the Item record. There are three options to set a value on the Asset Account or COGS Account field.

Choose an option:

1. Use the internal ID of the account. On the Field Mapping page, click the edit icon beside the Asset Account field. Click Choose Reference Type, and then select Internal ID.
2. Use the account name. In the CSV file, the asset account should have the same format used in NetSuite.
   1. Go to Lists > Accounting > Items.
   1. Click Edit on any item record.
   1. In the Asset Account field on the Accounting subtab, copy the format of the field to the CSV file. The format used is as follows:
      1. Account Number is not enabled: Parent Account
      1. Account Number is enabled: Number Parent Account
      1. Account Number is not enabled and there is a Child Account: Parent Account: Child Account
      1. Account Number is enabled and there is a Child Account: Number Parent Account: Child Account 
3. Set a default value for the asset or COGS account. This option is feasible if the same asset or COGS account is to be set on all of the item records. On the Field Mapping page, select Asset Account or COGS Account under NetSuite Fields. Click the edit icon, click Provide Default Value, and select the asset or COGS account.