> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-netsuite/integration-tools-and-methodologies/suitescript/n-record-module.md).

# N/Record Module

Learn how the N/Record module in SuiteScript helps integrate data by working with NetSuite records, even those not supported by CSV import.

The N/Record module serves as a pivotal tool in our integration strategy for working with NetSuite records. It is notably advantageous when [handling data not natively supported by NetSuite's CSV import functionality](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N356360.html#Supported-Record-Types-for-CSV-Import). For instance, NetSuite may not support the direct import of certain records, such as Shipment Receipts created in HotWax Commerce.

In such scenarios, we employ the N/Record module to bridge this gap. By writing SuiteScript, we can read CSV data from files located in SFTP locations, iterate through each record, and seamlessly create records in NetSuite's database. This process ensures the effective import of data into NetSuite for records that fall outside the scope of CSV Import methods.

Moreover, the N/Record module extends its capabilities to include the creation, deletion, copying, loading, or modification of standard NetSuite records. This versatile module plays a central role in our integration, facilitating the manipulation of native NetSuite records to achieve seamless data synchronization.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hotwax.co/documents/learn-netsuite/integration-tools-and-methodologies/suitescript/n-record-module.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
