You can view request and response errors from NetSuite and the Celigo NetSuite framework to debug errors if your account is on EM 2.0. integrator.io only supports NetSuite integrations that use the following protocols:
-
RESTlet 1.0
-
RESTlet 2.0/SDF
The request and response errors integrator.io displays are determined by the flow steps (import, export, etc.).
Use the Actions menu to view the request and response for any export or (dynamic) lookup that returns an error. The details displayed will vary depending on where the export or lookup failed.
Export errors have two classification types:
-
Handled/Intended errors - the export process (i.e. validation errors/valid saved search id) or the execution of savedSearch or a permissions-related error.
-
Unhandled/Uncaught/Not in control - infrastructure-related errors (i.e network-timeouts, NetSuite downtime, or NON HTTP 200 response use-case)
-
Any fatal errors leading to a search failure during export are denoted by a fatal node in the RESTlet response.
-
The following table displays an example of the request sent and the response that returns when NetSuite fails during the execution of a saved search. In this example, NetSuite received the request, but returned an error during the processing and execution of the saved search.
Request |
Response |
---|---|
Shows:
Example:
|
Shows the NetSuite nlapi response. Example:
|
The following table displays an example of the request sent and response that returns when NetSuite fails to process the request from integrator.io because of permission settings errors (not search or export errors).
Request |
Response |
---|---|
Shows:
|
Sample response: Example 1
Example 2
Example 3
|
Use the Actions menu to view the request and response for any import request that results in an error. The error details will vary depending on where the import failed.
Import errors have two classification types:
-
Handled/Intended errors - One or more are returned for each imported record in the request (i.e. import processes like mapping lookup failures, record save errors, record initialization errors.)
-
Unhandled/Uncaught/Not in control - infrastructure-related errors (i.e network-timeouts, NetSuite downtime, or NON HTTP 200 response use-case)
-
Any fatal errors leading to a search failure during export are denoted by a fatal node in the RESTlet response.
-
The following table displays an example of the request sent and the response returned when NetSuite fails during a lookup or mapping.
Request |
Response |
---|---|
Shows:
Sample request: Example 1
Example 2
|
Shows:
Sample request: Example 1
Example 2
|
The following table displays an example of the request sent and the response returned when NetSuite fails while processing nlapi requests submitted by the Celigo NS framework
Request |
Response |
---|---|
Shows:
|
Shows:
Example
|
The following table displays an example of the request sent and the response returned when NetSuite fails to respond to integrator.io.
Request |
Response |
---|---|
Shows:
The HTTP requests and responses are stored against every import object error. Example
|
Show:
Example 1
Example 2
Example 3
|