SuiteScript 2.1 Map/Reduce Script Reference

Map/reduce scripts are unique compared to other SuiteScript 2.1 script types, with distinct terminology and execution.

• To learn essential concepts behind map/reduce scripts, see Map/Reduce Key Concepts.

• 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.

• One major benefit of map/reduce scripts is their ability to manage some of their own resource usage. This is made possible by a feature called yielding. To learn more about yielding, see Map/Reduce Yielding.

• You can submit a map/reduce script in several ways. To learn how to submit a map/reduce script, see Map/Reduce Script Submission.

• Like all script types, map/reduce scripts have usage limits in NetSuite. To learn more about governance on map/reduce scripts, see Map/Reduce Governance.

• The Map/Reduce Script Status Page shows you script status and instance details. For more information about the Map/Reduce Script Status Page, see Map/Reduce Script Status Page.

• Like any SuiteScript 2.1 script, you'll need to test and potentially troubleshoot your map/reduce script. For more information about testing and troubleshooting map/reduce scripts, see Map/Reduce Script Testing and Troubleshooting.

• A map/reduce script can be interrupted by server issues or uncaught errors. 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.

General Notices