In NetSuite, User Event Scripts allow developers to execute custom logic at different stages of a record’s lifecycle. These scripts run on record types like Sales Orders, Invoices, or custom records, and are triggered during create, edit, delete, or view operations. The three key entry points for User Event Scripts are beforeLoad, beforeSubmit, and afterSubmit. Understanding their differences is essential for writing effective scripts.
1. beforeLoad
This trigger runs before the form is loaded and displayed to the user. It’s mainly used to modify the UI — for example, hiding fields, adding buttons, or setting default values. This function has access to the form object, making it ideal for customizing how the record appears on screen. However, it does not change the data saved in the database.
2. beforeSubmit
Executed before a record is saved to the database, this is the best place for data validation or modifying field values. For example, you can use it to auto-calculate a total, enforce business rules, or clean data before it is saved. Changes made here are saved along with the record.
3. afterSubmit
Triggered after the record is saved, this event is used for actions that rely on a saved record — such as sending emails, creating related records, or integrating with external systems. You cannot modify the record’s field values at this point since it’s already committed to the database.
Summary
Use beforeLoad to change the form UI.
Use beforeSubmit to validate or update data before saving.
Use afterSubmit for post-save actions like notifications or integrations.
Each stage serves a specific purpose, and choosing the right one ensures your custom logic works efficiently and without errors.