How to Correctly Resubmit NetSuite Records After Initial Script Failure?

When a script attempts to modify and resubmit a record after a previous submission failure, simply overriding the properties of the existing record object may not be sufficient. NetSuite's internal handling, potentially involving caching, can cause the system to retain the original error. To ensure successful resubmission, it is necessary to create a new record instance.

The recommended approach involves:

1. Loading the N/record module in your SuiteScript 2.x script.

2. Creating a new record object using record.create(). This ensures a fresh record instance, bypassing any cached states from previous failed attempts.

3. Populating this new record object with all necessary data.

4. Submitting the new record using record.save(). This operation consumes governance units, with costs varying based on the record type (e.g., custom vs. standard transaction records).

   Example of creating and saving a new record using SuiteScript 2.x:

javascript
// Ensure the 'record' module is loaded, e.g., define(['N/record'], function(record) { ... });

// Create a new record instance
var newSurvey = record.create({
    type: SURVEY_TYPE
});
// Populate newSurvey with necessary field values from the original failed record or new data
// For example: newSurvey.setValue({ fieldId: 'name', value: 'New Survey Name' });

// Submit the new record
var newSurveyId = newSurvey.save();

It is also considered best practice to verify the existence and active status of related records (such as contacts or customers) before attempting to submit the primary record, which can prevent common submission failures.