NetSuite Changelog
PlatformAPICustomizationReference

Services and Backend Models for Custom Modules in NetSuite

Explore how to use Services and Backend Models to create custom modules for accessing NetSuite records.

·1 min read·View Oracle Docs

If you need to create a custom module to access NetSuite records, read the following topics to learn how:

  • Define a JSON Object to Represent a NetSuite Record

  • Create a Backend Model

  • Create a Service to Handle HTTP Requests

Related Topics

  • SCA Models, Collections, and Services
  • Frontend Models
  • Collections
  • Services and Backend Models

General Notices

Frequently Asked Questions (4)

What is the purpose of defining a JSON object for a NetSuite record?
The purpose of defining a JSON object is to represent the NetSuite record structure. It includes name/value pairs for each custom field, and can include additional complexities like arrays or nested objects.
Are SuiteScript 2.0 features supported in backend models for NetSuite custom modules?
No, the code samples provided use SuiteScript 1.0 functions and objects only, and do not include SuiteScript 2.0 capabilities.
What are some common tasks required when creating a backend model in NetSuite?
Common tasks include defining dependencies, extending from SC.Model, defining a validation object, and defining methods to handle HTTP actions.
How do backend models handle HTTP requests in NetSuite custom modules?
Backend models typically handle HTTP requests by defining methods in the model to manage data transactions and perform operations on the NetSuite records.
Source: Services and Backend Models in Custom Modules — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Platform

View all Platform articles →