A
afterSubmit
User Event entry point that runs after a record is saved to the database. Used for sending emails, updating related records, or triggering workflows.
AMD (Asynchronous Module Definition)
The module loading pattern used by SuiteScript 2.x. Implemented via the define() function.
B
beforeLoad
User Event entry point that runs before a record is displayed. Used for form customization, adding buttons, or setting default values.
beforeSubmit
User Event entry point that runs after the user clicks Save but before the database write. Used for validation and data transformation.
C
Client Script
Script type that runs in the user's browser. Provides real-time field validation, UI interactions, and user feedback.
Context Object
Object passed to entry point functions containing information about the execution environment, such as context.newRecord, context.type, and context.form.
D
define()
AMD function that declares a module's dependencies and exports. First argument is array of module paths, second is callback function.
Deployment
Configuration that activates a script on specific records, roles, or schedules. Each script can have multiple deployments.
E
Entry Point
Function exported by a script that NetSuite calls at specific events. Examples: beforeLoad, afterSubmit, pageInit, onRequest.
Execution Log
NetSuite's logging system for scripts. Access via Customization > Scripting > Script Deployments > [deployment] > Execution Log.
F
File Cabinet
NetSuite's file storage system. Scripts are stored in Documents > Files > SuiteScripts folder.
fieldChanged
Client Script entry point that fires when a field value changes. Used for cascading updates and real-time calculations.
G
Governance
NetSuite's system for limiting script resource usage. Each operation consumes units; scripts have budgets (1,000-10,000 units depending on type).
getValue() / getText()
getValue() returns internal IDs; getText() returns display values. Essential for working with select fields.
M
Map/Reduce Script
Script type for processing large datasets. Has four stages: getInputData, map, reduce, summarize. Each stage gets fresh governance.
N
N/record
Module for creating, loading, copying, and saving records. Core operations: record.load(), record.create(), record.save().
N/search
Module for querying NetSuite data using filters and columns. Methods: search.create(), search.load().
N/query
Module for executing SuiteQL queries. Methods: query.runSuiteQL(), query.runSuiteQLPaged().
R
Records Catalog
NetSuite's schema browser for finding table names, column names, and join relationships. Access via Setup > Records Catalog.
RESTlet
Script type that creates REST API endpoints for external integrations. Supports GET, POST, PUT, DELETE methods.
S
Scheduled Script
Script type that runs on a schedule (e.g., daily, hourly). Has 10,000 governance units and can reschedule itself.
Suitelet
Script type that creates custom pages and forms. Accessed via URL, handles GET and POST requests.
SuiteQL
SQL-like query language for NetSuite. Executed via query.runSuiteQL(). Supports JOINs, GROUP BY, and standard SQL syntax.
submitFields()
Efficient method to update specific fields without loading the full record. Uses 10 governance units vs 20+ for load/save.
U
User Event Script
Script type that runs on record actions (create, edit, delete, view). Entry points: beforeLoad, beforeSubmit, afterSubmit.