How to Retrieve a Transaction ID in NetSuite After Submit Scripts?

To ensure the transaction ID is available in an afterSubmit script, implement one of the following methods:

1. Reload the Record (SuiteScript 2.x):

   The most direct approach is to reload the record within the afterSubmit script. This ensures that the script retrieves the most current state of the record, including the generated transaction ID.

javascript
    /**
     * @NApiVersion 2.x
     * @NScriptType UserEventScript
     */
    define(['N/record'], function(record) {
        function afterSubmit(scriptContext) {
            var newRecord = scriptContext.newRecord;
            var recordId = newRecord.id;
            var recordType = newRecord.type;

            // Reload the record to get the latest data, including the transaction ID
            var loadedRecord = record.load({
                type: recordType,
                id: recordId
            });

            var transactionId = loadedRecord.getValue({ fieldId: 'tranid' });
            log.debug('Transaction ID (reloaded)', transactionId);
            // Further processing using transactionId
        }
        return { afterSubmit: afterSubmit };
    });

1. Look Up the Field (SuiteScript 2.x):

   Alternatively, use search.lookupFields to retrieve specific fields, such as the transaction ID, from the saved record. This is often more efficient than loading the entire record if only a few fields are needed.

javascript
    /**
     * @NApiVersion 2.x
     * @NScriptType UserEventScript
     */
    define(['N/search'], function(search) {
        function afterSubmit(scriptContext) {
            var newRecord = scriptContext.newRecord;
            var recordId = newRecord.id;
            var recordType = newRecord.type;

            // Look up the 'tranid' field from the saved record
            var lookupResult = search.lookupFields({
                type: recordType,
                id: recordId,
                columns: ['tranid']
            });

            var transactionId = lookupResult.tranid;
            log.debug('Transaction ID (lookup)', transactionId);
            // Further processing using transactionId
        }
        return { afterSubmit: afterSubmit };
    });

1. Asynchronous Processing with Scheduled or Map/Reduce Scripts (SuiteScript 2.x):

   If the immediate availability of the transaction ID is not critical, or if the subsequent processing is resource-intensive or involves large datasets, consider an asynchronous approach. This offloads the processing to a separate script execution, preventing delays in the user interface.

   • Scheduled Script: For general asynchronous tasks, a SuiteScript 2.x scheduled script can be triggered to process the record after it has been fully committed. The afterSubmit script would simply enqueue the task for the scheduled script.
   • Map/Reduce Script: For processing large volumes of data, a Map/Reduce script is the recommended SuiteScript 2.x framework. The afterSubmit script could initiate a Map/Reduce job, passing the record ID for later processing.