- This topic has 1 reply, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
I have a generic orchestration handling different document types. The messages that I’m using inside the orchestration are of type XmlDocument, and this cannot be changed as the purpose of this orchestration is to be generic for many (similar) documents. However, when I send the message to the Send Port, the mappings specified in the port are NOT executed at all, even if the XmlDocument’s content is a perfectly valid document of a certain document type.
After some research, it seems that the BTS.MessageType property is not getting promoted, so the Send Port may not know which map to apply to it.
Does anyone know if what I’m attempting to do can even be done? Can I send a XmlDocument to a Send Port and expect the correct mapping to be applied?
Thanks
-
Tok,
You have the right idea in that it is the missing MessageType context property that causes the maps not to execute. Without it, BizTalk has no way of knowing which one of the multiple maps configured on a send port it should apply.
I haven’t tried what you’re doing but there might be a way of manually promoting the BTS.MessageType property yourself with the correct value from the orchestration (though I don’t know if this is possible with a raw XmlDocument untyped message).
You might also want to try and see if you can adapt the Dynamic Transforms in Orchestrations sample that Stephen has on this site [1] and do the transformations inside the orchestration itself instead of the send port. The sample is for 2006, but it might be possible to retrofit the solution to work with 2004.
[1] http://www.biztalkgurus.com/Samples/Dynamic-Transforms-BizTalk-2006.html
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.