The mapping of fields is an important step when importing data. When preparing an import file in a single file format, you have to import both line fields and body fields. The sub-list data consists of multiple lines for each sub-list item, you must provide a mapping to identify the record to which the sub-list belongs. Because the import file has more than one line we have to map each of the fields with the Net Suite fields.
In Net Suite, it is not necessary on the Field Mapping page of import assistant, but you have to include to uniquely identify the record when you use the single-file import format and you are importing new data. The unique ID must be included in every line of the CSV file. You will receive the following error when importing the file without the unique identifier:
“You must map one of the following Net Suite fields to a column in your CSV file, to be a unique identifier: External ID, Internal ID, or a transaction number field, such as Order # or Invoice #”
We will manually create the Internal ID when you import new data if the transaction ID is not yet available. The only unique identifier, in this case, is the External ID, and you must include it in each row of the file. You can use internal IDs for the same purpose when you update existing data.
At the time of import of new data, each record should be added with all the required body and sub-list fields. When you update existing records, you can update the values of body fields and sub-lists separately.
If your import file contains multiple lines of data for sublists, some lines of the sub-list data may be empty. If there are any empty columns in the raw data file, you have to fill the empty columns with appropriate values. The data in the import file should be consecutive when importing the file.
Mapping of fields when importing journal entry – Example
