Edit Flatfile disassembler - BizTalk 2004 Forum - BizTalk 2004

This is what I've managed to do:

I created one single schema that has an Envelope Node \"ENVs,\" and then have a Child Record under it that is the ENV structure itself. I leave the max and min occurences to the default (1), as my understanding is it will create a separate instance/xml file for each ENV.

I use ffdasm at the command prompt and get separate XML files. When I deploy my solution and run it, it fails. The stream errors in the middle of one of the children on the last line of the n-th ENV.

ex:

LIN|xyz|0*98|nop

* - where the stream stops.

I found that this is tied to the child delimter of 0x0D 0x0A being at the end of the last line. So I actually took it out (b/c suppressing trailing delimiters didn't seem to make a difference). I run the orchestration again, and it runs through...BUT, one large XML instead of separate ones. AND, when I run ffdasm at the command prompt, it fails giving me a similar error where the parsing fails in the middle of a field.
Quote
Subject:
Description: I re-read your response. So you don't think I should have an \"ENV's\" node, but rather JUST have the ENV under the schema node, and have the rest of my structure under that? [quote:ff47ea7676=\"Stephen W. Thomas\"]Hello. I would set this up putting the Envelope into the file. I would create a single schema like this: ENV|abc|123 HDR|def|456|!@# LIN||xyz|098|nop Then, used the native features of the Flat File Disassembler each message will be broken up and sent to the message box. So, if you message has 5 ENV you will get 5 messages. I would not message with a header. Do you think this would work for you?[/quote:ff47ea7676]
Tags

No results found