Home Page › Forums › BizTalk 2004 – BizTalk 2010 › FlatFileDisassembler doesn’t work
- This topic has 10 replies, 1 voice, and was last updated 9 years, 2 months ago by
community-content.
-
AuthorPosts
-
-
April 25, 2006 at 11:41 AM #14546
In the flatfile_body schema what is the maxOccurs attribute on the record, it should be 1.
If it is unbounded you will only receive 1 message because the parser will put each record into the first message.
If the record maxOccurs is 1 the parser will create 1 message with 1 record. -
April 25, 2006 at 11:59 AM #14547
Can you post your header and body schemas
-
April 25, 2006 at 12:14 PM #14548
That didn’t really worked as well as I hoped. I forgot about the size limit.
Can you email me the schemas-
April 26, 2006 at 1:45 PM #14549
The last probelm is caused by the Root element in your Receive_FlatFile_Body schema having a Child Order of Infix
You need to change this to Postfix.The previous error can be caused if the last record has no terminating \\r\\n (CRLF)
-
April 25, 2006 at 11:07 AM #14550
hi,
this is my situation.
I put in a folder the file \”OrderSystem_Output.txt\”
in this file you have this:
[quote:d6e6a3954b]Order_ID,Productname,Count
tg123,window,456
edkelp,somethinelse,1234[/quote:d6e6a3954b]so this file is received and a receivepipeline is invoked in the port.
in de pipeline you see in disassemble that there is a flatfiledisassembler where the document schema = flatfile_body
and the header schema = flatfile_headerthese two schema’s have been created with the flatfile-schema-wizard. and the flatfile is logicaly the \”OrderSystem_Output.txt\”
what do we do next, we transform the bodyschema to a sendschema where the relations are set correct.
and then it sends to a sendport who sends it to the message queue.what i get in the message queue is everything what is in the OrderSystem_Output.txt file. but in 1 queue-file.
I’d like to have this in multiple queue-file’s (for the size of records, if there are 5 records, there must be 5 queue-file’s. if there are 6, then it would be 6 queue-files)
But this without the header.But i don’t get that…
where did i do something wrong?kind regards
Thomas Desmet-
April 25, 2006 at 11:51 AM #14551
didn’t thought of that to fill in, so it stand on the default –> 1
now i see in my queue 1 message, with de header and all the records.
it must become several messages with one record.thx Thomas
-
April 25, 2006 at 12:11 PM #14552
I deleted this input for better cause
-
April 25, 2006 at 12:20 PM #14553
i just send you an email with it
-
April 25, 2006 at 1:29 PM #14554
yeah hi,
thx for your e-mail, i corrected them but still no working…
now i have an error in my event:
[quote:cd8a574d2f]There was a failure executing the receive pipeline: \”Webshop.ReceiveFlatFilePipeline, Webshop, Version=1.0.0.0, Culture=neutral, PublicKeyToken=bac8947f50b16b59\” Source: \”Flat file disassembler\” Receive Port: \”Webshop_1.0.0.0_Webshop.MainProcess_Receive_FlatFile_Ordersysteem_bac8947f50b16b59\” URI: \”d:\\FlatFile\\OrderSysteem_Output.txt\” Reason: Unexpected data found while looking for:
‘\\r\\n’
The current definition being parsed is Body. The stream offset where the error occured is 55. The line number where the error occured is 3. The column where the error occured is 7.
[/quote:cd8a574d2f]I have no idea what it could be…
Thx for looking.
Thomas-
April 25, 2006 at 2:41 PM #14555
mysteriesly it is solved i don’t know how but it suddenly did.
but new problem:
[quote:ca96c0ad89]<Root xmlns=\”http://Webshop.Receive_FlatFile_Body\”>
<Body xmlns=\”\”>
<Order_ID>gsgs</Order_ID>
<Productnaam>sdgfsdgf</Productnaam>
<Aantal>456..dfsfds,fzerj,789..raez,ezrytu,123</Aantal>
</Body>
</Root>
[/quote:ca96c0ad89]
that is my xml output that i get in my queue.instead of putting the rest in <Aantal> he should create a new XML document with the same root and everything, but other values.
hmmm…
Regards Thomas-
April 26, 2006 at 1:50 PM #14556
thx, problem solved with this.
Greets
-
-
-
-
-
-
-
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.