### Steps to reproduce

1. Send the following payload to the users api (e.g. `POST /api/v3/users` or `PATCH /api/v3/users/:id`): Begin of the insertion


End of the insertion Begin of the deletion



End of the deletion ```json
{
"name": "ABC"
}
```

### What is the buggy behavior?

* a 500 is produced

* The client gets no feedback that the field is Begin of the insertionread-onlyEnd of the insertion Begin of the deletion write onlyEnd of the deletion


### What is the expected behavior?

1. No 500

2. Ideally report that the field is Begin of the insertionread-only,End of the insertion Begin of the deletion write only,End of the deletion otherwise ignore the field.


###