Overview
When working with Suitelets in NetSuite, developers often encounter various errors that can hinder performance, functionality, and user experience. Understanding these common issues and their solutions ensures smooth execution and optimized Suitelet development. Below are some of the most frequent errors and how to resolve them.
Key Errors & Fixes
1. “You do not have permissions to access this record”
Cause:
The script is trying to access a record type for which the current user lacks permissions.
The script deployment role lacks the necessary access.
Solution:
Ensure that the script executes under a role with the correct permissions.
Navigate to Setup > Users/Roles > Manage Roles and grant the required record permissions.
Check the script deployment record to confirm it is running under the correct role.
Use runtime.getCurrentUser() to debug and verify the user’s role.
2. “NLAPI has been deprecated”
Cause:
SuiteScript 2.x uses a modular approach (N/Modules), while NLAPI functions are from SuiteScript 1.0, which is being phased out.
Solution:
Convert NLAPI functions to their SuiteScript 2.x equivalents.
Example:
// SuiteScript 1.0 (Deprecated)
var record = nlapiLoadRecord(‘customer’, 123);
// SuiteScript 2.x Equivalent
define([‘N/record’], function(record) {
var customerRecord = record.load({
type: record.Type.CUSTOMER,
id: 123
});
});
Reference NetSuite documentation for updated function mappings.
3. Suitelet Not Rendering Correctly
Cause:
Missing response handling (response.writePage() not called).
Incorrect HTML formatting when using response.write().
Solution:
Always call response.writePage(form) to ensure proper UI rendering.
Validate field values and field IDs to prevent errors.
Example of proper rendering:
define([‘N/ui/serverWidget’], function(serverWidget) {
function onRequest(context) {
var form = serverWidget.createForm({ title: ‘My Suitelet Form’ });
var field = form.addField({
id: ‘custpage_text’,
type: serverWidget.FieldType.TEXT,
label: ‘Enter Text’
});
context.response.writePage(form);
}
});
4. Session Timeouts & Authentication Issues
Cause:
The user’s session expired while interacting with the Suitelet.
API authentication failed due to incorrect credentials or token expiration.
Solution:
Implement Suitelet authentication using token-based authentication (TBA) or OAuth.
Use N/https for secure API calls and handle session validation.
Check and refresh authentication tokens regularly.
define([‘N/https’], function(https) {
function callSuitelet() {
var response = https.get({
url: ‘https://rest.netsuite.com/app/site/hosting/scriptlet.nl?script=123&deploy=1’
});
log.debug(‘Suitelet Response’, response.body);
}
});