Note: To apply these Netsuite Best Practices, you should be familiar with general Process Development, Building Connectors and the NetSuite Connector components.
Action Definitions
The Connector supports the following actions:
- Search - Returns one or more records that match zero or more filters.
- Get - Returns a single record that matches a given internal ID.
- Create - Creates a new record.
- Update - Modifies an existing record.
- Delete - Removes an existing record.
Note: Not all actions are available for every record type.
Querying Records
When querying records from NetSuite, each record found will be returned as a separate Document and be processed independently.
Updating Records
Updating a specific record in NetSuite requires that you include the internal or external NetSuite ID for that record in the update request.
As a best practice, if the other application has a field that can be used to capture an external ID, populate it with the NetSuite ID so you don't have to do a lookup to get the ID in your Process. Alternatively, use the user-specified external ID to maintain the "other" system's ID in NetSuite.
To do this, in the Map that maps from the source Profile to the NetSuite Update Profile, use a Map Function that performs a Connector Call to NetSuite. The Connector Call's Operation should do a Search action against the particular object type. Add a Filter to the Operation that you can pass in the key value(s) from the source data as an Input Parameter to limit the results to a single record. The Map Function should return the object's internalId attribute as an Output Parameter. Map this Output Parameter to the internalId attribute in the destination Profile.
If a particular object does not already exist in NetSuite, the internalId attribute in the Update Profile will be empty after the Map. If a request without an internalId is then sent to the NetSuite Connector, it will throw an error. If this is a possibility in your integration scenario, you should use a Decision Step after the Map to check that the internalId is populated in each record before sending the data to the NetSuite Connector.
Custom Fields and Objects
One of the great strengths of NetSuite is the ability to easily create custom fields and objects. Because of this, the NetSuite Connector connects to your NetSuite account and browses the available interfaces in real time. Custom objects and fields are handled no differently than standard objects and fields. If you modify an object in NetSuite after importing it in Boomi, you will need to edit the Operation Component and go through the import wizard again to re-import the recent changes.
Understanding the Netsuite Date Format
NetSuite Date/Time XML Profile elements should be configured with the following format:
yyyy-MM-dd'T'HH:mm:ss.SSSZZ
For example: 2010-04-01T10:33:17.837-07:00
Batching Requests to NetSuite
To maintain satisfactory performance for all of its clients, NetSuite governs the web service traffic sent to its data center. There are limits on the number of records per request by the type of request (Add vs. Update vs. Search) as well as time of day (peak vs. off peak). For example, you cannot try to add more than 100 records at once during the middle of the day, but at night that limits grows to 200. Refer to the NetSuite Help Center, Understanding Web Services Governance, for more information.
However, the NetSuite Connector automatically batches the records to the proper size in accordance with NetSuite's guidelines. This means your Process can send any number of records to the NetSuite Connector and it will chunk the records automatically for you.
Other Technical Notes
- The Connector does not necessarily open and close a connection per batch. It pools up to four connections for efficiency.
- Requests are sent synchronously.
- Request batches are sent sequentially, not concurrently.
Additional Resources
NetSuite Help Center
(Navigate to SuiteFlex --> SuiteTalk --> Platform Guide or Records Guide)
This page
Other pages
Account
