On Thu, 02 Aug 2007 20:14:16 +0200, Jan Eliasen
<eliasen@[EMAIL PROTECTED]
> wrote:
>Feel free to email me your schema and sample instance - I will take a
>look at it.
And you did :-)
I don't believe this is a bug as much as a design issue. It makes
sense, that if you have five fields, that are delimited infix by "^",
then the "^" must be there four times. In your example, you have
several "|" just after eachother. So if a field is missing, the
delimiter should still be there.
The error has nothing to do with mapping. It is the flat file
disassembler that uses the schema to parse the file.
If five fields are possible, but only one delimiter (as in your test
file in your project), how is BizTalk supposed to know which two of
the five fields the values belong to?
Right now, as you have seen, BizTalk guesses the data belongs to the
last optional fields - you need them in the first optional fields. But
what if someone sends the second and fourth field and a delimiter in
between? I don't onsider this a bug at all. I think your trading
partner should have the delimiter present... it is the nicest way to
do it. The way they do it now, you can not parse the flat file without
using business logic that says if fields are not present, they wont be
present from the right. This is a silly restriction, when you could
just have the delimiters and always parse the file right.
Hope this helps, allthough it doesn't help :-)
--
eliasen, representing himself and not the company he works for.
Private blog: http://blog.eliasen.dk
Private email: jan@[EMAIL PROTECTED]
|
