FIX: The xsl:for-each statement is put at the parent field of the child field of the destination schema in BizTalk Server 2004

Article translations Article translations
Article ID: 838572 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you use a Looping functoid, a Conditional functoid, or a Value Mapping functoid, an xsl:for-each statement is generated in the compiled map. If the child field of the destination schema has unbounded maximum occurrences, the xsl:for-each statement is put at the child field. If the child field does not have unbounded maximum occurrences, the xsl:for-each statement is put at the parent field of the child field.

However, because the different locations of the xsl:for-each statement affect the map result, you may want the xsl:for-each statement to be put at the child field of the destination schema, regardless of whether the maximum occurrence of the child field is set to 1.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751 How to obtain the latest BizTalk Server 2004 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version     Size       File name
   ------------------------------------------------------------------------------------------
   17-Mar-2004  21:14  3.0.5260.0    676,864  Btsxmltools.dll
   17-Mar-2004  20:37  3.0.5260.0    274,432  Microsoft.biztalk.basefunctoids.dll
   17-Mar-2004  21:13  3.0.5260.0     45,056  Microsoft.biztalk.crossreferencing.dll
   17-Mar-2004  20:52  3.0.5260.0     40,960  Microsoft.biztalk.crossreferencingfunctoids.dll
   17-Mar-2004  20:51  3.0.5260.0    249,856  Microsoft.biztalk.mapper.dll
   17-Mar-2004  20:51  3.0.5260.0  1,114,112  Microsoft.biztalk.tom.dll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

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

This problem was corrected in BizTalk Server 2004 Service Pack 1.

MORE INFORMATION

After you apply this hotfix, you must add the following attribute in your map (.btm) file:
TreatElementsAsRecords="Yes"
This setting does not appear in the UI. To add this attribute, you must edit the map file in a text editor such as Notepad. The following is an example of the edited code:
<mapsource Name="BizTalk Map" BizTalkServerMapperTool_Version="2.0" Version="2" 
XRange="100" YRange="420" OmitXmlDeclaration="Yes" TreatElementsAsRecords="Yes" 
CopyPIs="No" method="xml"… >
When this attribute is set to Yes, the xsl:for-each statement is put at the child field of the destination schema, regardless of whether the maximum occurrence of the child field is set to 1.

For more information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 838572 - Last Review: July 17, 2006 - Revision: 3.1
APPLIES TO
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition
Keywords: 
kbbiztalk2004-2006swept kbbiztalk2004sp1fix kbqfe kbfix kbbug kbhotfixserver KB838572

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com