[rt-users] REST and umlauts in Custom Field names

[Christian Loos]

Am 11.12.2014 um 15:31 schrieb Jasper Olbrich:
> Hello,
> 
> I'm trying to use REST to create tickets in a queue that uses Custom
> Fields. It works well for CFs without umlauts, but I couldn't find a way
> yet to fill the CF "Größe".
> 
> I'm sending the data with Python's urllib module, the request body looks
> like
> 
> content=id%3A+ticket%2Fnew%0AQueue%3A+Test-Queue%0ARequestor%3A+jasper.olbrich%40students.uni-marburg.de%0ASubject%3A+Encoding+von+CustomFields%0AText%3A+%3CThe+ticket+content%3E%0ACF-Gr%C3%B6%C3%9Fe%3A+A0%0ACF-working%3A+working&user=$user&pass=$pass
> 
> 
> where CF-Gr%C3%B6%C3%9Fe is the urlencoded CF name. I also tried to
> circumvent urlencoding for this particular CF name:
> 
> content=id%3A+ticket%2Fnew%0AQueue%3A+Test-Queue%0ARequestor%3A+jasper.olbrich%40students.uni-marburg.de%0ASubject%3A+Encoding+von+CustomFields%0AText%3A+%3CThe+ticket+content%3E%0ACF-working%3A+working%0ACF-Gr\xc3\xb6\xc3\x9fe%3A+A0&user=$user&pass=$pass
> 
> 
> "\xc3\xb6\xc3\x9" is the byte sequence for utf-8 encoded unicode "öß".
> 
> I also tried to add "charset=utf-8" to the content encoding header, but
> to no avail.
> 
> Is it possible to write CFs via REST? Reading works fine.
> 

Hi,

use CF-123 (with 123 being the CF id).

Chris