Share via

EDI pipeline with character set Extended

  • Article

Receiving German Characters in the EDI message received by Biztalk 2006 R2. We have set the character set to "Extended" in the receive pipeline but it still fails in the receive pipeline.

Solution:

Found that the char set ‘Extended’ does not include the complete iso8859-1. It implements subset of the 8859-1 . The following is the list of characters in integers that we support/consider under `Extended` 32-93, 95, 97-126, 161, 191-194, 196, 199-202, 204-206, 209-212, 214, 217-220, 224-226, 228, 231-239, 241-244, 246, 249-252. The list of characters that we support under `Extended` are clearly a subset of ISO8859-1. For all chars outside of this list, we should use UTF8. We found that the messages received by Biztalk was not proper UTF8 as it was missing BOM headers. Once we added the BOM headers it worked with character set UTF8.

Comments

  • Anonymous
    January 22, 2010
    The comment has been removed
  • Anonymous
    January 25, 2010
    This works for both X12 and EDIFACT.Can you confirm if the message is not missing BOM headers? You can try opening the message in a notepad and save it after selecting encoding as UTF-8 and try it again using a File Adapter.
  • Anonymous
    May 08, 2011
    Hi Atin,Hope you remember me from hawaii client.How to add the BOM headers to BizTalk.my outbound EDIFACT is having German characters and it is failing while sending out of  EDI pipeline.Thanks...Surya
  • Anonymous
    May 08, 2011
    Surya, check out blogs.msdn.com/.../utf-encoded-message-failing-in-biztalk-2006.aspx onhow to add BOM Headers.Atin
  • Anonymous
    May 11, 2011
    Thanks Atin,That information is real helpful.