10.07.2015 Views

SuiteTalk (Web Services) Platform Guide - NetSuite

SuiteTalk (Web Services) Platform Guide - NetSuite

SuiteTalk (Web Services) Platform Guide - NetSuite

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Web</strong> <strong>Services</strong> Error Handling and Error CodesUnderstanding <strong>Web</strong> <strong>Services</strong> Warnings, Errors, and Faults271You can set a company wide preference on the <strong>Web</strong> <strong>Services</strong> Preferences page on how to handlewarnings or you can specify how warnings should be handled in a specific request. Requestlevel preferences override company-wide preferences. Refer to Setting Company-widePreferences for information on how to set company-wide preferences.Following is an example of a warning message in the response to a request to add a customerrecord without a zip code (with the Treat Warnings as Errors preference set to false):WARNINGWithout a zip/postal code it will not be possible to usethis address with 3rd Party shippers. Click Cancel to edit the address.The above customer was added because no error occurred. However, future errors could beavoided by responding appropriately to the warning message.For a detailed list of all warning messages and the associated codes generated by <strong>NetSuite</strong>, seeWarning Status Codes.ErrorsErrors result if invalid or incomplete data is submitted when performing an operation. Forexample, if a client attempts to update a customer record with an invalid internal ID, theoperation fails and the response contains an error code and message.When numerous records are submitted within the same request, each is treated individually.For example, if a client attempts to update two events within the same request, where onerecord has invalid data and the other has valid data, only one of the records has an error and isnot updated.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!