if I got a map/reduce and it call record.save, when will the record actully save? after all setvalue or by request?

AI generated answer (using internal Slack threads):

In a Map/Reduce script in NetSuite, the record will actually save when the

record.save

method is called. This can be done in either the Map stage or the Reduce stage, depending on your specific use case. If you're setting multiple values on a record, you can call

record.setValue

for each field you want to change, and then call

record.save

once you've set all the values. The record won't actually save until the

record.save

method is called, so it will save after all

setValue

calls have been made. Here's a simplified example of how you might do this in a Map/Reduce script:

javascript
function map(context) {
    var record = record.load({
        type: context.key,
        id: context.value
    });

    record.setValue({
        fieldId: 'field1',
        value: 'new value 1'
    });

    record.setValue({
        fieldId: 'field2',
        value: 'new value 2'
    });

    // The record will save after all setValue calls have been made
    record.save();
}

Remember, the

record.save

method is a request to NetSuite to save the record, so the actual save operation may not happen immediately if the system is busy, but it will be queued and executed as soon as possible. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******