Can You Import Quality Inspection Sublists via CSV?

Short answer: no, not directly. NetSuite's CSV Import Assistant does not expose the Quality Inspection sublists, Data Fields, Inspection Standards, or Pass/Fail Criteria, as mappable columns when you import a qualityinspection record. The import template stops at the header-level fields. If you've been adding those sublist rows manually after every import, you're not missing a hidden checkbox. The UI simply doesn't offer it.

That said, there are two workable paths: a separate import for the underlying lists, and a SuiteScript for the actual association. Here's what actually works.

What the CSV Import Assistant Shows for Quality Inspection

When you go to Transactions > Management > Import Records > CSV Import and select Quality Inspection as the record type, the Field Mapping page lists header fields like trandate, location, item, quantity, and createdfrom. The sublist IDs, inspectionfield and inspectionstandard, never appear in the mapping dropdown.

This is consistent with how NetSuite treats most sublists in CSV import. The official documentation on sublist data import confirms that if you don't map any fields for a sublist, no sublist data gets imported. The Quality Inspection sublists simply aren't among the supported ones for import.

The "Overwrite Sublists" option you'll see on the Field Mapping page? It applies to sublists that the import actually supports. For Quality Inspection, it's effectively a no-op.

What You Can Import Separately

There is one partial win. You can import the Quality Inspection Fields List, the master list of inspection fields that get referenced on the Quality Inspection record.

Go to Setup > Import/Export > Import CSV Records and look for Quality Inspection Fields List as the record type. This populates the inspectionfield records themselves. You can also import the Quality Standards Fields List, which feeds the iteminspectionstandard record's standardfield field.

But here's the gap: neither import lets you associate a specific Data Field with a specific Quality Inspection record. You end up with a library of fields and standards, but the linking step on the Quality Inspection record still requires manual entry or a script.

The SuiteScript Path: Associating Sublist Rows

If you're importing Quality Inspections in bulk and need the sublist rows populated automatically, SuiteScript is the only reliable route. Here's the pattern that works in production.

You'll load the Quality Inspection record and use selectNewLine / setCurrentSublistValue / commitLine on the inspectionfield sublist. The field IDs you need are inspectionfield (the field reference) and fieldvalue (the value entered).

/**
 * @NApiVersion 2.1
 * @NScriptType UserEventScript
 * @NModuleScope SameAccount
 */
define(['N/record', 'N/log'], (record, log) => {
    function beforeSubmit(context) {
        if (context.type !== context.UserEventType.CREATE) return;
        
        const qaRec = context.newRecord;
        const fieldId = 123; // internal ID from Quality Inspection Fields List
        const fieldValue = 'Pass';
        
        qaRec.selectNewLine({ sublistId: 'inspectionfield' });
        qaRec.setCurrentSublistValue({
            sublistId: 'inspectionfield',
            fieldId: 'inspectionfield',
            value: fieldId
        });
        qaRec.setCurrentSublistValue({
            sublistId: 'inspectionfield',
            fieldId: 'fieldvalue',
            value: fieldValue
        });
        qaRec.commitLine({ sublistId: 'inspectionfield' });
        
        log.audit({
            title: 'Inspection Field Added',
            details: `Added field ${fieldId} with value ${fieldValue}`
        });
    }
    
    return { beforeSubmit };
});

For Inspection Standards, the sublist ID is inspectionstandard, and you'll set the standard field with the internal ID of the iteminspectionstandard record.

Why Manual Entry Is the Real Bottleneck

The reason this trips people up: the Quality Inspection record is often created from a Work Order or Item Receipt via a Create button. When you do that, NetSuite automatically populates the Inspection Standards sublist from the item's default standards. The Data Fields sublist, however, stays empty until someone fills it in.

So if you're importing Quality Inspections as standalone records, you lose that automatic population. The script above restores it by copying standards from the item or by applying a predefined field set.

What About the "Overwrite Sublists" Option?

The Overwrite Sublists checkbox on the CSV Import Field Mapping page has a specific behavior documented in NetSuite's import guidelines. When set to True, the import completely replaces all existing sublist values with the CSV data. When False, behavior varies by sublist type:

• Keyed sublists (those with a unique key field) update matching rows.
• Non-keyed sublists append all CSV rows as new lines.

Neither behavior applies to Quality Inspection sublists because the import doesn't expose them. If you see the checkbox, it's a generic UI element that doesn't change what you can map.

The Pragmatic Takeaway

If you're doing occasional Quality Inspection imports, keep adding sublist rows manually. It's tedious but simple. If you're importing dozens or hundreds at a time, write the UserEventScript above, deploy it to the qualityinspection record, and trigger it on create. It'll run under the same governance budget as any other beforeSubmit script, and it's fast enough that you won't notice the units consumed.

One edge case to watch: if your CSV import creates the Quality Inspection and then you immediately edit sublist rows in the UI, the beforeSubmit script may conflict with your manual changes. Restrict the script to run only when a custom field or memo value indicates the record came from an import, or gate it behind a checkbox you set during the import mapping.

For the Inspection Standards side, you can also pre-populate the Item Inspection Standard records per item, so the script only needs to copy them over rather than look them up. That keeps the script lean and the data consistent.

SuiteScript is the only path that gets you fully automated sublist population.