NetSuite connector for Jitterbit Integration Studio
Summary
The NetSuite connector establishes access to NetSuite.
The NetSuite connector provides an interface for creating a NetSuite connection, the foundation used for generating instances of NetSuite activities. These activities, once configured, interact with NetSuite through the connection.
The NetSuite connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).
Tip
Integration recipes and process templates are available for this connector through Jitterbit Marketplace.
Connector overview
This connector is used to first configure a NetSuite connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
Together, a specific NetSuite connection and its activities are referred to as a NetSuite endpoint:
-
Search: Retrieves existing records from NetSuite and is intended to be used as a source to provide data in an operation.
-
Create: Creates new records in NetSuite and is intended to be used as a target in an operation.
-
Update: Updates existing records in NetSuite and is intended to be used as a target in an operation.
-
Get List: Retrieves a list of existing records based on ID from NetSuite and is intended to be used as a target in an operation.
-
Upsert: Both updates existing records and creates new records in NetSuite and is intended to be used as a target in an operation.
-
Delete: Deletes records in NetSuite and is intended to be used as a target in an operation.
Note
This connector is a native Integration Studio connector, which may be referred to by Jitterbit when communicating changes made to connectors. The release schedule for native Integration Studio connectors is based on the cadence of Harmony portal web applications.
Prerequisites and supported API versions
Certain prerequisites must be met to use this connector, including having token-based authentication (TBA) enabled, using a supported NetSuite WSDL version, and using Harmony cloud or private agents that support the NetSuite WSDL version.
The NetSuite connector uses the SOAP web services API of the version of the NetSuite WSDL you have configured. The NetSuite connector can be configured with the supported WSDLs listed in the prerequisites.
Refer to documentation provided in the NetSuite Help Center for information on the schema fields.
Limitations
The NetSuite connector does not support attach / detach web services. To use these web services, use Jitterbit's SOAP connector.
Troubleshooting and how-tos
Troubleshooting
If you experience issues with the NetSuite connector, these troubleshooting steps are recommended:
-
Ensure the NetSuite connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
-
Check the operation logs for any information written during execution of the operation.
-
Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.
-
If using private agents, ensure you are using agent version 11.30 or later and check the agent logs for more information.
-
Review the NetSuite connector's limitations.
If you are still experiencing issues, there are general troubleshooting considerations in Operation troubleshooting, and the following pages provide further troubleshooting information specific to the NetSuite connector:
-
Concurrency governance: What to do if you see errors caused by too many concurrent requests.
-
Custom fields: How to expose custom fields for an object when using a private agent.
-
Custom segments: What to check if custom segments aren't displayed as expected.
-
Data center error: A workaround for an error related to an incorrect data center.
-
Permissions error: A workaround for an error regarding insufficient permissions.
-
Record limits: Recommendations on enabling chunking if you run into NetSuite API record limits.
How-tos
In addition to the troubleshooting information above, the following how-to pages provide detailed instructions on accomplishing specific tasks with integration projects that use the NetSuite connector:
-
Enable multi-currency in NetSuite: How to enable the multi-currency feature in NetSuite.
-
Enable NetSuite asynchronous requests: How to set the Jitterbit variable
jitterbit.netsuite.async
to use periodic polling. -
Enable TBA in NetSuite: How to enable token-based authentication in Netsuite prior to configuring a NetSuite connection.
-
Gather values for using NetSuite TBA: How to gather values needed for configuring a NetSuite connection.
-
Pass NULL values to NetSuite custom fields: How to set custom fields to NULL in a transformation.
-
Search by status in NetSuite: How to specify the correct search filter value when configuring a NetSuite Search activity.
-
Use a NetSuite account-specific WSDL URL: How to obtain an account-specific WSDL URL required for configuring a NetSuite connection.
-
Use NetSuite functions: How to use a NetSuite connection with NetSuite functions.
-
Use standard forms in NetSuite: How to use standard forms for custom objects in NetSuite.
Additional resources
A Jitterbit microlearning tutorial is available through our Jitterbit basics video series: