Anyone know off hand the best way to handle unicod...
# suitetalkapi
b
Anyone know off hand the best way to handle unicode characters when dealing with REST api? I think NS doesn't like them. I'm currently sending them encoded. For example:
Copy code
HTTP PATCH <https://ABC123.suitetalk.api.netsuite.com/services/rest/record/v1/itemfulfillment/12345678?replace=package>

{"carrierform":"fedex","shipMethod":{"id":"1234"},"shipStatus":"C","package":{"items":[{"packageDescr":"V\u00C1MONOS:","packageTrackingNumber":"1234567890","packageTrackingNumberReturn":"","packageWeight":15}]}}
But get back 500 error:
Copy code
{
  "type": "<https://www.rfc-editor.org/rfc/rfc9110.html#section-15.6.1>",
  "title": "Internal Server Error",
  "status": 500,
  "o:errorDetails": [
    {
      "detail": "An unexpected error occurred. Error ID: lx3a59z615mtxd5Xc5m3f",
      "o:errorCode": "UNEXPECTED_ERROR"
    }
  ]
}
I'm assuming it is related to the unicode characters
v
Have you tried sending the actual Á ?
b
Not yet, but plan to. After some more digging, I see this same error response in other cases intermittently where there aren't any escaped Unicode characters.