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

This article has been archived. It is offered "as is" and will no longer be updated.
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

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File 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: 01/17/2015 07:29:55 - Revision: 4.0

  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition
  • kbnosurvey kbarchive kbautohotfix kbbiztalk2004-2006swept kbbiztalk2004sp1fix kbqfe kbfix kbbug kbhotfixserver KB838572
Feedback