BizTalk Server does not route a document correctly based on promoted properties in a BizTalk Server 2006 R2 environment

When you receive an XML document that contains several promoted attribute properties in a Microsoft BizTalk Server 2006 R2 environment, BizTalk Server does not route the document correctly based on these promoted properties.

This problem occurs if an element that is represented in minimized tag syntax (also known as a self-terminating element) contains the promoted attributes. For example, the following code sample contains a self-terminating element:If the name attribute in the schema that you deploy to BizTalk Server is a promoted property, BizTalk Server does not promote the content of this element when BizTalk Server processes the element through the receive pipeline. However, if the data is represented in a paired element tag, the property promotion works as expected. For example, the following code sample contains a paired element tag:

To work around this problem, use one of the following methods:

• Use a map during pipeline processing. When you do this, BizTalk Server creates the end tag.
• Use a custom pipeline component to handle promotion of these values. That is, use a custom pipeline component to add a closing element for the record before BizTalk Server passes the record to the XML disassembler.

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