Item or custom list translations cannot be imported
Check language setup, translation mappings, and whether the main record needs to be created first.
Creating an item with translations reports Locale
Message may mention: Locale.
What it means
Creating the item and its translations together can cause this documented failure.
Import context: Inventory items and Item translations.
Check this first
First add the item with its required accounting, location, and pricing data, then update it with language and translated display values.
Show the steps
Check how the detail rows are linked
- Confirm whether this is a single-file or multiple-file import.
- Identify the parent record key and the key used to connect each detail file.
- Verify that every required detail row points to an intended parent, with no spelling or whitespace changes in the linking value.
- Check the import's field mapping for the detail sublist. Defaults alone do not establish that detail rows were imported.
- Separate a record identifier from a line identifier. They serve different purposes.
For assemblies, link member rows to the assembly. For routings, check the operation sequence within each routing. For customer/contact combinations, keep each record's identity and fields separate. Check the actual mapping fields for the record being imported.
If that looks right
In the first pass, include the starting quantity price break when required. In the second pass, use Update and map the translation language and translated display name to the translation sublist.
Documentation checked September 16, 2026.
A translation line cannot be added
Message may mention: translations.
What it means
Translation support may not be configured.
Import context: Custom lists.
Check this first
Check that the language feature is enabled and at least one language is configured.
Show the steps
Check the required field and mapping
- Find the exact NetSuite field named in the error. Confirm whether it belongs to the record header, a line, or a subrecord.
- Check that it is mapped to the intended CSV column, or to a valid default.
- Inspect the affected records for missing values. A populated column does not mean every record has a value.
- Expand the relevant field group in the mapping tree. A required field can be present there without being visible in the current mapping list.
- If the field belongs to a sublist, make sure the import actually supplies that sublist's data.
For a field that cannot be written, inspect its availability and the import's read-only-field setting. Ignoring a read-only field allows the rest of the import to proceed; it does not make the field editable. Read-only fields
If a custom field is required, provide the intended value first. Turning off mandatory custom-field validation changes which incomplete records the import will accept. It should be an informed configuration choice, not the default troubleshooting instruction. Mandatory custom fields
Documentation checked September 16, 2026.
Translation rows do not match the default language
Message may mention: translations.
What it means
One default language may be applied to rows containing several languages.
Import context: Custom lists.
Check this first
Map the language from the file instead.
Show the steps
Check how the detail rows are linked
- Confirm whether this is a single-file or multiple-file import.
- Identify the parent record key and the key used to connect each detail file.
- Verify that every required detail row points to an intended parent, with no spelling or whitespace changes in the linking value.
- Check the import's field mapping for the detail sublist. Defaults alone do not establish that detail rows were imported.
- Separate a record identifier from a line identifier. They serve different purposes.
For assemblies, link member rows to the assembly. For routings, check the operation sequence within each routing. For customer/contact combinations, keep each record's identity and fields separate. Check the actual mapping fields for the record being imported.
Documentation checked September 16, 2026.
Related errors
- Customer type or linked contact data needs attention
- A required field is missing or cannot be written
- NetSuite cannot read the CSV file or its columns
- Sales order terms and payment method conflict
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite