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

Re: simple call to another orchestration

BizTalk 2013

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

simple call to another orchestration

Not Answered This question is not answered


I'm fairly new to BizTalk and I'm trying to do a simple call to another orchestration.  I don't need to send a message to the called orchestration, just bool input and out params.  I was able to successfully configure the call orch shape using the in and out variable params I set up, but when building the project I get the below error:

'you must specify at least one already-initialized correlation set for a non-activation receive that is on a non-selfcorrelating port' 

Do I need a correlation set since I'm not sending messages between the caller and callee?  I've seen examples where they didn't set up correlation sets but they were sending messages back and forth. 

thank you for any help.

All Replies
  • Hi,

     You get this error because you have a Receive shape in your secondary orchestration that is called by your primary orchestration. Take this receive shape out of the designer view in your secondary (called) orchestration, and you should be all set.

     Good luck.

    "Google skills are more important than your coding skills."

    • Top 10 Contributor
  • Thanks so much for your response.  But I need a receive shape in my called orchestration.  The idea is that I'll have a main orchestration start up, make an entry to a sql table for processStart with dates, etc, then call several other orchestrations that will work with different types of messages.  Those orchestrations will each have a receive shape for a different message.  I thought it would be better to break it up into several orchestrations rather than have one with so many shapes.  Would it make a difference if I used 'start' orchestration rather than 'call' orchestration?

    • Top 500 Contributor
  • Hi,

     From your calling orchestration, you can pass different message type to each of your called orchestration as a parameter, like I said in my earlier post, you need to get rid of the Receive shape in your called orchestration. Using a Start orchestration shape vs. a Call orchestration does not matter in your scenario unless you expect to do an asynchronous call in the former vs. a synchronous call in the latter.

    "Google skills are more important than your coding skills."

    • Top 10 Contributor
  • Hi,

    Have you set the Activate property to True on the first Receive Shape?

Page 1 of 1 (5 items)