Yes that was one big mistake. I was looking for the EDIInt.MessageId property but I had to make reference to EDI base artifacts dll to use that property as a correlation ser definition.
The problem right now is that if I use EDIInt.MessageId or EDIInt.OriginalMessageId the orchestration stops working because the message doesn’t have that property (the AS2 properties are attached after the pipeline process the message, I think) so I’m promoting that property using MyMessage(EDIInt.OriginalMessageId) = XXX and MyMessage(EDIInt.MessageId) = XXX
So this forces that my returning MDN has as returning OriginalMessageId = XXX (so basically if my correlation set is set to use the OriginalMessageId and in both messages I have the same then the message should be correlated right?
Also I don’t now if this a problem but I’m receiving the mdn message in my orchestration as a Xlang.Any type (not sure the complete namepspace) becasue I don’t know how MDN should be created. Heres were I get the info (http://killustar.blogspot.com/2008/01/receiving-as2-mdn-in-biztalk.html). Should this be a problem? should I create an schema for the MDN?
Thanks for your time