VERSICH

Fixed: NetSuite Transaction CSV Import Issue “Could not find matching record...”

fixed: netsuite transaction csv import issue “could not find matching record...”

While attempting to carry out a CSV import to modify a single checkbox on sales orders in NetSuite, this error emerged, hindering a successful import. Here’s how to fix it.

During a straightforward CSV import aimed at updating a single checkbox on sales order records in NetSuite, the following error occurred, blocking the import from completing successfully:

Error: "Could not find matching record. Primary name field was not mapped or is empty."

Understanding CSV File Data Formatting

The CSV file used for the import originally included several lines of data, with some entries left blank because they weren’t necessary for this import.

The initial version of the CSV file contained data for import, data that would be excluded during the import, and columns that solely had headers.

Our CSV Import Mapping in NetSuite

In the NetSuite Import Assistant, the data handling was configured to Update, and the mapping included only the internal ID of the sales order and the checkbox set to a hardcoded value of True.

The Import Error and Unique Features of This Issue

This error frequently arises during customer imports when the customer ID hasn’t been accurately mapped. In this specific import, however, there was no mention of the customer record. The data did not include any hidden characters that could interfere with the internal ID value.

How We Fixed This NetSuite CSV Import Error

Ultimately, the resolution involved deleting any unnecessary columns from the CSV file and rerunning the import. It is essential to eliminate columns that contain extraneous data (not just the data itself) to avoid encountering another error. The import mapping remained unchanged.