simple call to another orchestration

Home Page › Forums › BizTalk 2013 & BizTalk 2013 R2 › simple call to another orchestration

Viewing 2 reply threads
  • Author
    Posts
    • June 25, 2014 at 7:03 PM #27964
      community-content

        Hello,

        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.

      • June 25, 2014 at 8:32 PM #28019
        community-content

          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.

          • June 26, 2014 at 4:14 PM #28042
            community-content

              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?

              • June 26, 2014 at 8:17 PM #28054
                community-content

                  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.

            • August 21, 2014 at 4:04 AM #28021
              community-content

                Hi,

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

            • Author
              Posts
            Viewing 2 reply threads
            • The forum ‘BizTalk 2013 & BizTalk 2013 R2’ is closed to new topics and replies.