Microsoft KB Archive/304565

= PRB: Message Fields Are Converted to String Data Type in the Orchestration Designer =

Article ID: 304565

Article Last Modified on 11/5/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition

-



This article was previously published under Q304565



SYMPTOMS
When you add new message fields from a schema that was created with the BizTalk Editor to a port in the BizTalk Orchestration Designer, the XML data types that are used in the schema are converted to a String data type.



CAUSE
This behavior occurs because the XLANG engine works with OLE compatible data types. Each XML data type that is used in the schedule must have a corresponding data type that is OLE compatible, otherwise it will be converted to a String OLE compatible data type. For example, an XML data type of Enumeration does not have an OLE compatible data type. Therefore, it is converted to a String data type. The exceptions to this rule are the Bin.hex and Bin.base64 data types, which will also be converted to a String data type.



STATUS
This behavior is by design.



MORE INFORMATION
The following table maps XML data types to their corresponding OLE compatible data types:

Bin.base64 and Bin.hex data types, and any XML data types that do not have corresponding OLE compatible data types will be converted to the String OLE compatible data type by the XLANG engine.

Keywords: kbprb KB304565

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.