Integrating Integrators – BizTalk, Windows Azure, Windows Workflow, and Beyond

Re: Receive binary file correlated on RecievedFileName

BizTalk 2010

This group is for all content related to BizTalk Server 2010. This includes a forum and samples.

Receive binary file correlated on RecievedFileName

Answered (Verified) This question is answered

Hi

I'm having problem with routing a message of binary file to a receive location using correlation. The correlation is initialized using a send with dummy file where i in Orchestration set the ReceivedFileName context property of the message and the property gets promoted. After that routing fails of the message being received and i can see that the ReveivedFileName context property of that message has not been promoted should it be like that? i cant figure out any way to get it promoted so i just want to make sure it should be like this.

The file names are identical but i noticed that the ReceivedFileName property of the send message doesn't have the path whereas the received message has path + file name. i have tried to add the path to the send message(sounds strange though, read it some where) but it doesn't change the outcome.

Regards Robert

Verified Answer
  • I was unable to promote the property by using correlation in Orchestration . i tried your solution but didn't work alone however also calling Context.Promote for the ReceivedFileName property did the trick! Feels like over doing it by having to resort to custom pipeline though. Thanks for the point in the right direction! :)

    Regards Robert

    • Top 150 Contributor
All Replies
  • You can fix this in the custom Receive pipeline by removing the extra path so both ReceivedFileName context properties will have same value.

    Regards,
    NISHIL
    MCT,MCTS | Freelance BizTalk Consultant.
    biztalkconnect.blogspot.com

    • Top 10 Contributor
  • I was unable to promote the property by using correlation in Orchestration . i tried your solution but didn't work alone however also calling Context.Promote for the ReceivedFileName property did the trick! Feels like over doing it by having to resort to custom pipeline though. Thanks for the point in the right direction! :)

    Regards Robert

    • Top 150 Contributor
Page 1 of 1 (3 items)