Discussions
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
NSC | REST WS: Empty External ID
When working with NetSuite's REST API, attempting to set a record's External ID to an empty string can lead to unexpected behavior. Instead of successfully updating the External ID field, the API responds with a
{
"type": "XXX",
"title": "Bad Request",
"status": 400,
"o:errorDetails": [
{
"detail": "Invalid value '' for the field externalid.",
"o:errorPath": "externalid",
"o:errorCode": "INVALID_VALUE"
}
]
}
In conclusion, while NetSuite's REST API offers extensive capabilities for interacting with NetSuite data, developers must be mindful of constraints such as the inability to set External IDs to empty strings.
The sample code described herein is provided on an "as is" basis, without warranty of any kind, to the fullest extent permitted by law. Oracle + NetSuite Inc. does not warrant or guarantee the individual success developers may have in implementing the sample code on their development platforms or in using their own Web server configurations.
Richard James Uri - SuiteCloud | WMS Tech | SuiteCommerce Advanced
----
- NetSuite Admin Corner | New to NetSuite
- Explore the NSC Webinars Category
- Join our poll and share your ideas! We want to know what you think. Don't forget to comment and make your voice heard!
