On Wed, Aug 11, 2010 at 02:18:51AM -0700, FOSTER Ryan * SDC wrote: > I am using the REST interface to create and update tickets, as described > in the wiki > ([1]http://wiki.bestpractical.com/view/REST). However, I am running into a > problem with some > custom fields that have a hash/pound symbol (#) as part of the name. Other > custom fields work > fine. > > For example, when attempting to update a ticket I get a response like this: > > RT/3.8.1 409 Syntax Error > # Syntax error. > cf-A Custom Field: aaa > >> cf-Another Field #: 123 > cf-Contact Name: Ryan > > I get the same error whether I url encode the data or not. Is there a > special way to escape or > encode special characters to avoid this error?
Have you made it work with bin/rt and looked at the generated data using RTDEBUG=3 bin/rt ? -kevin
pgpRdNz8wp7lE.pgp
Description: PGP signature
RT Training in Washington DC, USA on Oct 25 & 26 2010 Last one this year -- Learn how to get the most out of RT!
