The below setting is somewhat misunderstood:

If you are to set this setting, what is passed to the Message Box, and what is the behavior.

To simulate this, I created a send port with the following setting:

When I ran the 867 (found in the samples folder of the SDK) I got the following error message:

There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “XML assembler” Send Port: “EDI Drop Off” URI: “C:\Users\Administrator\Documents\Visual Studio 2008\Projects\EDI\Output\%MessageID%.xml” Reason: This Assembler cannot retrieve a document specification using this type:

I could not find the schema in the BizTalk 2009 folder.

Here is the data that is created by the EDI DASM with the Preserve Interchange setting:

<ins0:X12InterchangeXml DelimiterSetSerializedData="126:13:10:42:58:-1:-1:-1:-1" xmlns:ins0="">
  <ns0:ISA xmlns:ns0="">
    <ISA02>          </ISA02>
    <ISA04>          </ISA04>
    <ISA06>7654321        </ISA06>
    <ISA08>1234567        </ISA08>
  <FunctionalGroup DocType="">
    <ns0:GS xmlns:ns0="">
    <TransactionSet DocType="">
      <ns0:X12_00401_864 xmlns:ns0="">
    <ns0:GE xmlns:ns0="">
  <ns0:IEA xmlns:ns0="">

So what can consume this message?

If you look at Preserving a Received Batched EDI Interchange, it does not explain about what happens to the document.

If you look at Sending a Preserved Batch Interchange, it will recreate the interchange based on the settings described on the page.

I asked why there is this option, to preserve interchange, getting a document that is only consumable by the EDI ASM, and was told that you can create a map that transforms all of the EDI transactions from one to another and keep the batch together, however this does not seem correct, because a map would be looking for a MessageType of, not

It seems that this is only for validation, or re-enveloping.