Article ID: 297651
Article Last Modified on 10/17/2003
APPLIES TO
- Microsoft BizTalk Server 2000 Standard Edition
This article was previously published under Q297651
SYMPTOMS
When you use both a logical functoid and a normal link as input to a destination record, the BizTalk Mapper may generate incorrect XSLT code.
For example, you may expect output that is similar to the following, in which the attribute for an element is defined before the content for the element is generated:
<BlankSpecification>
<ADDLINE index="0">1st row</ADDLINE>
<ADDLINE index="2">3rd row</ADDLINE>
</BlankSpecification>
However, when this problem occurs, you may receive output that is similar to the following, in which the content for an element is generated before the attribute is defined:
<BlankSpecification>
1st row
<ADDLINE index="0" />
3rd row
<ADDLINE index="2" />
</BlankSpecification>
In this example, the ADDLINE record has both a logical functoid and a normal link from a source field as input.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft BizTalk Server 2000 Service Pack 1.
Keywords: kbbug kbfix kbbiztalk2000sp1fix KB297651
