The import has no linked item, expense, or member lines
Check the detail mapping and how each item, expense, member, or operation row connects to its parent record.
- The assembly has no linked member items (Assemblies)
- The cost template has no linked cost lines (Manufacturing cost templates)
- The report has no linked expense line (Expense reports)
- An invoice has no item line (Invoices and credits)
- The routing has no linked operations (Manufacturing routings)
- A sales order has no item line (Sales orders)
The assembly has no linked member items
Message looks like
Please select member items before submitting
What it means
The assembly import reached NetSuite without any member items attached, so the assembly cannot be built as a bill of materials.
Import context: Assemblies.
Check this first
Check the link between the assembly file and the member file: the member rows must carry the assembly identifier.
Show the steps
Steps for this error
- For a multiple-file import, confirm the member file links to the assembly file through Assembly Item: External ID, Internal ID, or Name.
- Use Items as the import type with Assembly/BOM Item as the record type, upload the assembly file as the primary file and the members as the linked Item Members file, and set Data Handling to Add.
- Map the member name and quantity to Item and Quantity in the Item Members folder, then retry one assembly.
If that looks right
Documentation checked September 16, 2026.
The cost template has no linked cost lines
Message looks like
You must enter at least one line
What it means
The cost template saved without any cost lines. In a multiple-file import this usually means the key column linking template to detail rows did not match.
Import context: Manufacturing cost templates.
Check this first
Check that every template has at least one detail row and that the linking key matches exactly in both files.
Show the steps
Steps for this error
- Confirm every cost template record has at least one cost line in the file.
- For a multiple-file import, check the key column linking the template file to its detail file. A typo in that column breaks the link.
- Retry one template.
If that looks right
Documentation checked September 16, 2026.
The report has no linked expense line
Message looks like
You must enter at least one line item for this transaction
What it means
An expense report saved without any expense lines, which usually means the key column linking the report file to the expense file did not match.
Import context: Expense reports.
Check this first
Check that every report has at least one expense row and that the linking key matches exactly in both files.
Show the steps
Steps for this error
- Confirm every expense report record has at least one expense line in the file.
- For a multiple-file import, check the key column linking the report file to its expense file. A typo in that column breaks the link.
- Retry one report.
If that looks right
Documentation checked September 16, 2026.
An invoice has no item line
Message looks like
You must enter at least one line item for this transaction
What it means
The invoice saved without any item line. A default value on the item mapping does not create a line; the item must come from a CSV column.
Import context: Invoices and credits.
Check this first
Put the item in its own column and map it to the Items : Item field on the Field Mapping page.
Show the steps
Steps for this error
- Confirm the file contains an item value on every intended invoice line.
- Map that column to the Items : Item field on the Field Mapping page and check the key linking each line to its invoice header. For a new invoice, set Data Handling to Add.
- Retry one invoice and verify that its item line was created.
If that looks right
Documentation checked September 16, 2026.
The routing has no linked operations
Message looks like
You must enter at least one line
What it means
A routing saved without any operation lines, which usually means the key linking the routing file to its operations file did not match.
Import context: Manufacturing routings.
Check this first
Check that every routing has operations and that the linking key matches exactly in both files.
Show the steps
Steps for this error
- Confirm every routing record has at least one operation line in the file.
- For a multiple-file import, check the key column linking the routing file to its operations file. A typo in that column breaks the link.
- Retry one routing.
If that looks right
Documentation checked September 16, 2026.
A sales order has no item line
Message looks like
You must enter at least one line item for this transaction
What it means
The sales order saved without any item line reaching its Items sublist. A default value on sublist fields does not create lines; at least one sublist field must be mapped from the file.
Import context: Sales orders.
Check this first
Check that every order has an item row and that the line data links to its order header.
Show the steps
Steps for this error
- Confirm each intended sales order has at least one CSV row containing an item.
- Map that value to the sales-order Items sublist and verify how detail rows link to the header.
- Retry one order and inspect its resulting item lines.
If that looks right
Documentation checked September 16, 2026.
Related errors
- An item on a received line cannot be changed
- NetSuite cannot match a transaction or location line
- Vendor bill files or purchase order mappings conflict
- NetSuite cannot apply a payment or credit
Book a free 30-minute look at your import error
Bring the error and your file to a screen share and I will dig into it live. Thirty minutes is usually enough to find what is wrong and tell you what fixing it takes. Sometimes that settles it on the call; when it does not, you leave with a straight answer instead of a mystery. No cost and no obligation.
An import that keeps failing is often the first visible sign of a larger setup problem. Most of my client work starts exactly here: somebody mid-import, a file that will not load, and nobody on their side to email. If a migration or implementation sits behind this error, that is the work I do every week.