List of bugs that are fixed in BizTalk Accelerator for SWIFT 2.1 Service Pack 1 (922264)

MORE INFORMATION

For more information about the bugs that are fixed in BizTalk Accelerator for SWIFT 2.1 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base: The following issues are also fixed in this service pack. These issues will be discussed in an upcoming Knowledge Base article:

• You receive a "'TimeAndInputReference' element has an invalid value" error message when you process an MT082 message.
• An invalid SWIFT message is suspended. However, the message is not passed to an error-handling pipeline as expected.
• An MT300 message incorrectly fails validation.
• You receive a "The 'LTAddress' element has an invalid value according to its data type" error message when you process an MT202 message.
• The MRSRHelper class intermittently throws an error when an empty result set is returned.
• Microsoft InfoPath forms are updated to improve data persistence.
• An exception occurs when the GlobalTrackingOption property has a value of 0.
• User access auditing when changes are made to the Message Repair & Submission Runtime (MRSR) orchestration is now supported.
• You receive a BREValidation error code T52 when you process an MT535 message.
• You receive an "Unexpected data found" error message when you process an MT392 message.
• You cannot open an MT202 message in the MRSR orchestration.
• An MT201 incorrectly fails validation.
• You cannot use universal groups to configure the Accelerator for SWIFT.
• You receive a BREValidation error code D19 when you process an MT103PLUS message.

The following issues are also fixed in this hotfix package. These issues were not previously documented in a Microsoft Knowledge Base article:

• You receive an "Unexpected data found" error message when you process an MT760 message.
• You receive a BREValidation error code T40 when you process an MT210 message.
• Error messages that appear on InfoPath forms are improved.
• A blank line is unexpectedly removed from field 50 of an MT210 message.
• The Message User Reference (MUR) is not validated correctly according to the SWIFT specifications. Before you install this service pack, there is no restriction on the number of characters in the MUR field. According to the SWIFT specifications, the MUR field should be limited to 16 characters.
• You receive a "The 'TextBlock' element has an invalid value" error message when you try to process a valid MT094 message.
• The Receiver Bank Identification Code (BIC) can be in lowercase in a SWIFT message header.
• You receive a BREValidation error code K94 when you process an MT547 message.
• You receive a "The 'RateTypeCode' element has an invalid value" error message when you process a SWIFT outgoing message of type 564.
• You receive an incorrect BREValidation error code E83 when you process an MT586 message.
• You receive a "The 'Line4' element has an invalid value according to its data type" error message when you process an MT305 message.
• The MRSR orchestration is updated.

The following issue is also fixed in BizTalk Accelerator for SWIFT 2.1 SP1:

• Blank spaces in header fields and in positional fields are not preserved in an output flat file. This issue occurs when you use receive pipelines and send pipelines that contain SWIFT Disassembler components and SWIFT Assembler components to process SWIFT FIN messages.

Note To resolve this issue, you must also apply the hotfix that is described in the following Knowledge Base article: