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.
Oracle + NetSuite Inc. does not warrant, guarantee or make any representations regarding the use, results of use, accuracy, timeliness or completeness of any data or information relating to the sample code. Oracle + NetSuite Inc. disclaims all warranties, express or implied, and in particular, disclaims all warranties of merchantability, fitness for a particular purpose, and warranties related to the code, or any service or software related thereto.
Oracle + NetSuite Inc. shall not be liable for any direct, indirect or consequential damages or costs of any type arising out of any action taken by you or others related to the sample code.
To know more about REST Web services Operations, check these New to NetSuite Articles.
Do you have another way on how to resolve an external ID error in REST WS? Feel free to share them here!
If you find this information useful, let us know by reacting or commenting on this post! Thank you!