BUG: The TargetCharset value in an XMLTransmit pipeline configuration may not take effect as expected in BizTalk Server 2006

In Microsoft BizTalk Server 2006, the TargetCharset value for an XML Transmit pipeline may not take effect as expected.

For example, you receive a message that uses the UTF-8 encoding format. However, you want the outgoing message to use the UTF-16 encoding format. Therefore, you set the TargetCharset value in the XMLTransmit pipeline to Big-Endian-UTF16 (1201). However, the outgoing message may unexpectedly use the UTF-8 encoding format.

To work around this issue, use one of the following methods.

Method 1: Use a custom pipeline

To work around this issue, use a custom pipeline to send the messages. For example, set the Target charset property in the XML assembler component of the custom pipeline as follows:

• To use the UTF-8 encoding format, set the Target charset property to UTF-8 (65001).
• To use UTF-16 encoding format, set the Target charset property to Big-Endian-UTF16 (1201) or Little-Endian-UTF16 (1200).

Method 2: Use an orchestration

To work around this issue, use a construct shape in an orchestration to correctly set the encoding value. For example, add a MessageAssignment shape to a new orchestration. Next, double-click the MessageAssignment shape. Then, type the following code in the BizTalk Expression Editor.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.