[Bug] Update task name with Sonderzeichen fails if not escaped

Developer Forum
1

What happened?
Sending the following UTF-8 JSON to /api/v1/tasks/${task.id}:

{
  "id": "b1b6721e-77cd-4235-910a-97ccc5a561f1",
  "name": "AWK-1005 Jour Fix 2 durchführen"
}

Results in error:

{
  "code": "validation-failed",
  "description": "The model sent in the request is invalid. See the validation errors for details.",
  "link": "https://developers.awork.com",
  "validationErrors": [
    {
      "property": "$.name",
      "message": "The JSON value could not be converted to System.String. Path: $.name | LineNumber: 0 | BytePositionInLine: 85."
    }
  ]
}

We only set the Content-Type and Authorization Headers. The reason seems to be the ü character in the name.

–

We implemented a workarround by escaping all Sonderzeichen using the unicode escape seqences

{
  "id": "b1b6721e-77cd-4235-910a-97ccc5a561f1",
  "name": "AWK-1005 Jour Fix 2 durchf\u00FChren"
}

Maybe we also need to set a header for the encoding?

What is the Trace-Id of the request?
Trace-id: 3ee0ee3e09c7754b526dd3b336c280d3

2

Sending special characters, especially Umlaut, should not be an issue. I’ve tested this as well and have no issue creating a task. The character you are sending shows up as � in our logs, so I wonder if it is something else or a special version.

Other than the content-type, there is no other encoding you need to set.