Error Handling in Searches with SuiteScript 2.0 Features

When using SuiteScript 2.0 for searches, understanding error handling is crucial for developers and administrators. This article covers the potential errors encountered when loading searches and offers practical solutions.

What Errors Can Occur?

When you attempt to load a saved search using the search.load(options) method, the following errors may arise:

INVALID_SEARCH

• Message: That search or mass update does not exist.
• Thrown If: The system cannot find a saved search matching the options.id provided.

SSS_MISSING_REQD_ARGUMENT

• Message: {1}: Missing a required argument: {2}
• Thrown If: A required parameter is absent in the request.

Code Example for Loading a Search

Here’s a sample code snippet demonstrating how to load a saved search using SuiteScript:

var mySearch = search.load({
    id: 'customsearch_my_so_search'
});

This code attempts to load a saved search with the specified id. If the saved search does not exist, it will trigger the INVALID_SEARCH error.

Supported Script Types

The search.load method can be used in both client and server scripts. It is essential to ensure that the proper script types are employed when implementing this function.

Governance

Using the search.load method consumes 5 governance units for each execution. Therefore, be mindful of your current governance units to avoid exceeding your limits.

Conclusion

Error handling when loading searches is a vital aspect that developers must manage effectively. Understanding the potential errors and their solutions is crucial for streamlined application development in NetSuite.

Source: This article is based on Oracle's official NetSuite documentation.