realize it's probably bad form to post follow-ups to one's own messages, but I've been doing some additional research in an attempt to avoid unpleasant surprises down the road. I still need to solve the problem listed in the first message in this thread, but I believe I've found another one waiting to be uncovered.
If I manually update my sample input document instance to include the Tag Identifier values for each row, I can get the instance to validate successfully, but only if the detail rows are in sequence (which they will not be in the real documents I need to process) or if there are only one of each record type. I have been experimenting - unsuccessfully - with the Group Order Type property of the document root node, which seems to be what will control this part of the document schema. This is what the BizTalk Server documentation says about this property:
All: Specifies the element group as an all group. All groups allow their child elements to appear zero (0) or one (1) time, and in any order, in instance messages. Restrictions apply; see remarks for more information.
Choice: Specifies the element group as a choice group. A choice group allows only one of its child elements to appear in instance messages.
Sequence: Specifies the element group as a sequence group. Sequence groups require that child elements in instance messages appear in the same order as defined in the schema. This is the default value.
None of these values appear to do what I need. Currently, using "Sequence" as the Group Order Type property value I can parse this document instance (where the detail records appear in the same order as they are defined in the schema):
but can not parse this one (where the detail records appear in the pseudo-random order in which they will appear in "live" documents):
I have been unable to find *any* information about parsing this type of flat file using BizTalk Server 2004, which has been very frustrating. I have, however, found EDI samples in the BizTalk SDK that appear to do what I need. The X124010850Schema.xsd EDI schema from the sample in %InstallFolder%\EDI\Adapter\Getting Started with EDI\Visual Studio Projects\Getting Started with EDI\Session 1 appears to do what I need, but I cannot see how it does it. This EDI schema has the Group Order Type value of "Sequence" but in the sample instance documents included with the EDI sample application the various child nodes (such as PER and PID) appear repeatedly.
Is there a way to support this type of flat file in BizTalk Server 2004?
----- Matthew Roche wrote: -----
I have a delimited flat file being produced by a legacy system that
contains a variety of different record types. I need to create a flat file
schema so that I can map these records to SQL Server stored procedures using
the SQL Adapter and enter their data into a SQL Server database. I'v