Forum Replies Created
-
Posts
-
You could just add a FlatFile schema with this structure
Root (delimited PostFix Hex 0x0D 0x0A)
–Document (delimited InFix Hex 0x0D 0x0A maxOccurs=unbounded)
—-Header (Positional, Tag Identifier=10)
——You header elements here
—-Items(delimited InFix Hex 0x0D 0x0A)
——Item(Positional, Tag Identifier=40 maxOccurs=unbounded)
——–your item elements here[quote user="Anonymous"]
The above schema design is absolutely possible use Flat -File shema wizard for this schema design.
[/quote]
How? 🙂
I found the problem…I changed the user under the identity tab from 'SHARON\IWAM_SHARON' to the user created in the domain.
You need to have it matched the encoding the document you're receiving is actually encoded in; it's not about guessing or a predefined value. Some editors can try (and often very successfully do) guess the encoding of the document, like VS. I'd try opening the file in VS and then going to the File -> Advanced Save Options menu item; it will display the encoding being used. Chances are if the document looks OK in VS, then using whatever encoding VS is using will work.
I think you need to use the Listen Shape.
The Parallel action shape will wait until all the actions are completed. And in your case you will only ever receive one message.
Hope this helps.
Thanks for your post.
So in my scenario, What Code Page, i need to use for my Schema, UTF-8 or Western-European (1252), Inorder to handle all international characters.
I appreciate.
Thanks
MS Learning has a free Assessment on BizTalk 2006: http://assessment.learning.microsoft.com/test/home.asp
That might help.
I generally try to avoid using the sample BizTalk MSI installer.
I've had alot more success using Scott Colestock's Deployment Framework for deploying BizTalk, and it solves alot of additional problems which the base MSI installer ignores as well. You can find that at http://www.traceofthought.com
You will have to learn NAnt to make that framework work, but it's worth it. (Not to mention NAnt is a good skill, and very portable to MSBuild under .NET 2.0)
Seems odd to me that MSFT tells you it need to be a System.String and then it does work.
Maybe you have to use a specific type of pipeline?
Sorry, I don’t know what else to say…
You probably have the wrong encoding when processing the file. Here's a description of how the Flat File disassembler guesses the encoding of the received message and what you can use to signal it to use the right encoding:
http://www.winterdom.com/weblog/2005/09/08/SelectingTheEncodingUsedWhenParsingFlatFiles.aspx
Yea, I wish this was a non-multipart message, but with HL7 it will need to be.
I have been following the instructions given from microsoft and it appears the z-segment needs to be System.String. I tried using system.xml.xmldocument and the segment never made it to the outgoing message.
The only other idea that I had was to wrap my string in xml and hope that the disassembler recognized it, but it appears that is just replaces any < and > tags with the xml compliant tags, < and >.
I am not sure where to go from here….
