SuiteScript 2.x Map/Reduce Script Reference

Map/reduce scripts are different than other SuiteScript 2.x script types, specifically in their terminology and in the way they are executed.

To learn about terms specific to map/reduce scripts, see Map/Reduce Terminology.
To learn about how map/reduce scripts are executed in stages, see Map/Reduce Script Stages.
A key advantage of the map/reduce script type is that it can manage some aspects of its own resource consumption. This behavior is achieved through a feature known as yielding. To learn more about yielding, see Map/Reduce Yielding.
There are several ways to submit a map/reduce script for execution. To learn how to submit a map/reduce script, see Map/Reduce Script Submission.
As with all script types, NetSuite imposes usage limits on map/reduce scripts. To learn more about governance on map/reduce scripts, see Map/Reduce Governance.
The Map/Reduce Script Status Page allows you to view script status and details of script instances. For more information about the Map/Reduce Script Status Page, see Map/Reduce Script Status Page.
As with any SuiteScript 2.x script type, you need to test and may need to troubleshoot your map/reduce script. For more information about testing and troubleshooting map/reduce scripts, see Map/Reduce Script Testing and Troubleshooting.
Execution of a map/reduce script can be interrupted by an application-server disruption or by an uncaught error. To learn how to handle these errors, see Map/Reduce Script Error Handling.
To learn about best practices for working with map/reduce scripts, see Map/Reduce Script Best Practices.