Common Custom Module Errors

The following table describes common custom module errors and how to resolve them:

Error Message

Description

Module not found

You'll see this error if you use the require function. Because require doesn't have a global context, relative paths won't work unless you import require() as a dependency of the define function.

For more information, see require Function and define Object.

Module does not exist

Try switching from relative paths to absolute paths.

You do not have permission to load this module

Check the module scope settings. For details, see SuiteScript Module Scope and Access Control.

Script is behaving inconsistently or erratically

If your script uses a custom module or library, make sure the file is in a File Cabinet location without restrictions. Files and folders inherit parent folder restrictions, which can prevent some roles from running the script.

Related Topics

General Notices