Thread: OTM 4.5 not handling Non Ascii Characters
View Single Post
  #3 (permalink)  
Old July 23rd, 2007, 20:03
AlejandroBarba AlejandroBarba is offline
Senior Member and Blogger
  
Join Date: Nov 2006
Location: San Diego, CA
Posts: 76
Blog Entries: 2
Groans: 0
Groaned at 0 Times in 0 Posts
Thanks: 0
Thanked 18 Times in 17 Posts
Rep Power: 3
AlejandroBarba is on a distinguished road
Re: OTM 4.5 not handling Non Ascii Characters
Hi,

We had a similar issue but for inbound order transmissions where the character "&" is part of the Shipper contact. The issue was solved by adding the "amp;" suffix so we would have "&" instead of "&".

If you are talking about inbound transmissions, I would refer to the Integration manual to check how to change the encoding in the header to include non 7bit ASCII characters.

Hope this helps,

Alejandro B.
Reply With Quote