Topic by MTSponeal
Content
Hi, I am working with the connectAPI wth Java pulling down threads (e.g. the text exchanges between our agents and our customers) and I am running into cases where the content of the thread contains some characters that seem to be throwing off the parsing of the SOAP response when my client is reading it. We deal with customers and technical issues so the thread text can contain all sorts of characters, code samples, etc.
I am wondering the best way to get around this? I am using an Analytics report to fetch the thread data and I see i can pass a boolean to have the response encoded as base64 (referring to http://documentation.custhelp.com/euf/assets/devdocs/november2012/Connect_Web_Services_for_SOAP/Default.htm, the 'ReturnRawResult' argument)
Does anyone have experience doing this? Is this how to get around the issue with unexpected characters in the XML response or might there be another alternative? Any pointers or ideas would be appreciated!
Thank you..and Merry Christmas :-)