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.
Method 1: Use a custom pipelineTo 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 orchestrationTo 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.
<Message_Name>(XMLNORM.TargetCharset) = "unicode";
Article ID: 939550 - Last Review: Sep 10, 2008 - Revision: 1