Forum Replies Created
-
Posts
-
this was a fantastic help in getting me started… http://msdn2.microsoft.com/en-us/library/aa547055.aspx
This will fix you right up!
BTS.InterchangeSequenceNumber
Pomoted by the Messaging Engine after receiving a message from the receive adapter and before publishing it into the MessageBox database.
xs:int
Indicates the sequence number of the document in the interchange. If the document is not part of an interchange that was disassembled into individual documents, then this value will be 1. The property can be read in an orchestration, a send pipeline and send adapter.
From: http://msdn2.microsoft.com/en-us/library/aa562116.aspx
According to this it should be 1 if nothing else.
I need to do something similar and was going to just use a .NET compnent when someone pointed me to "Pro BizTalk 2006", Chapter 5 (ISBN: 1-59059-699-4).
I need to take more than 100 files in a batch and compress and send them individually via http://ftp. Since I can file drop them locally, I can setup a receive pipleline to take care of this after the batch completes or at anytime we need. Don't forget file naming standards as well.
What about:
<DATA>
<Borrower id=1 LastName="" FirstName="" MiddleName="" SSN=""/>
<Borrower id=2 LastName="" FirstName="" MiddleName="" SSN=""/>
…
</DATA>- Sometimes I like to ask: Why are you doing it this way?
I should have a few cycles this evening to test this scenario for myself to see what the problem could be. If I don't see a post that you've solved this I'll test it and provide any feedback I can.
Great advice.
This piece of the application reads the XML file, maps it to another message that will be passed to a web service. I'll get a response back, but I only check it for verification/debugging. This whole process is in its own orchestration and is very simple at this point. The rest of the orchestration should work (famous last words) if I could only get past loading my XML file.
The overall application will be handling a few different XML files. All of the XML files have a root element of "Header". I started using the default XMLReceive pipeline, but since all of the XML files coming in have the same root element it seemed that I needed to create a custom pipeline for each XML file type. There are not many schemas that I'm working with, so I don't have a problem with multiple custom receive pipelines.
I just tried adding an inbound map to the receive port. The same error came up as before ("No Disassemble stage components can recognize the data.").
Your suggestions and questions are a great help. Much appreciated.
Anonymous,
in general I don't see how BizTalk can give you this. For example, suppose my app drops a file for you – which app was it?
The message context gives you lots of information (for example the filename is there was one) which you may be able to use to deduce the originating app. But in general, how could BizTalk know?
John D.
Wincy,
normally you should do this by the use of "child order". This can be either prefix, infix or postfix. It tells the assembler where to put record delimiters. I guess you need Postfix – that is, put delimiters (CR/LF) at the end of each record.
John D.
In AX3.0 Biztalk Adapter is not there.
so for that u need to use AX 4.0 (which is having Biztalk Adapter and also including Webservices)
Well Anonymous.
Output of Logical functiod should be the first parameter to the Value mapping functiod.
I have mentioned the same.
Biztron….its true we should delete the MAP and create a new MAP..
Later in some other project while having free time one should try debugging wht went wrong.
I just tested string concat with "true" and & (anded) them together, then value mapped a string based on the result. "true" & "true" = true.
Also, I used an equal (=) with a concat of "true" = "true" and anded that result from the "=" and the other "true". true & "true" = true.
Then I changed one of the concats to "false"… true & "false" = false ..and.. false & "true" = false.
Now I need to modify the custom functoid and test it in the AM.
Thanks for the help.
I just tested this scenario stated by NISHIL, and it worked exactly as you would expect. I have run into the problem as stated by "-weak architect" so he probably has loads of experience to recognize this.
After you verify that I think you should have it. You can always import the schema and map from the other project but I'm sure this would be a waste of time. If their suggestions don't work…which they obviously should, then I would recommend either deleting and replacing the functoids, or create a new map to test that one scenario. It only took me a few minutes to set this up with a project open already.
Michael,
First thing is to use the XML Disassembler if you need one in the first place. You should not use the Flat file disassembler for an XML file.
Then my obvious question, and forgive me for not knowing this already, is can you parse this message without a pipeline? There are so many choices here to receive and map your input. I found that I only add complexity when required.
- Is there no way to add inbound maps to your Receive port to help distinguish the schema or even to map to your own internal schema that you control…thus isolating you from external changes?
- Are there so many potential schemas that make using multiple receive ports impractical?
- Can you elaborate on what you're doing with the messages once you receive them? Are you combining data, passing through, writing to a DB, etc?
I'm not sure I'd go down the path of UTF-8 v. UTF-16 until you verify the simple things first. I think I (we all) can help some more but I think the understanding the pattern/solution you're trying to accomplish would help.
- I would suggest if you want to or need to use an XML disassembler, first try with something REALLY simple and add complexity after testing it a few times. This one process has saved me days of wheel spinning when trying something new.
It is an XML file. I've tried both XML Disassembler as well as the flat file disassembler.
The "Validate Instance Input Type" is OK.
The error shown above is when I use the flat file disassembler. When I try the XML disassembler I get this error:
"FlatFileTest_1.0.0.0_FlatFileTest.WPayment_PaymentInPort_ea895c3799b5f29e" URI: "d:\installs\biztalk\*.payment" Reason: No Disassemble stage components can recognize the data.
Which approach is more appropriate to take? I've Googled this message and it appears that I need to convert the file to UTF-8 from UTF-16 to get around it. Is there another way? This workaround seems very strange to me.
Thanks. This is very helpful.
Anonymous,
first of all you need an adapter to enable the conversation between BizTalk and Axapta.
This could be a web service adapter. Does Axapta offer a web service interface?
There is also (if you Google) at least one dedicated adapter for Axapta to BizTalk.
After that you will need some BizTalk knowledge…
John D.
