Re: Direct binding to MsgBox
- From: "Leo Gan" <leo_gan_57@xxxxxxxxxxx>
- Date: Fri, 14 Jul 2006 13:20:06 -0700
Bob is right that you shouldn't need a pipeline here. However, one thingI think there is used term the *demote* (?)
to watch out for is that doing as bob mentions above won't actually
*promote* the property value, it will only write it into the message
context and, so, it won't be used for message routing, which might be the
problem Guy is facing.
--
Regards
Leonid Ganeline
BizTalk Solution Developer
===========================
http://geekswithblogs.com/leonidganeline
================================
"Tomas Restrepo (MVP)" <tomasr@xxxxxxxx> wrote in message
news:%23Kc6AbapGHA.516@xxxxxxxxxxxxxxxxxxxxxxx
Bob, Guy,
You shouldn't need to use a pipeline to set your context value for this.
As
long as the property is promoted as opposed to distinguished (and it can
be
either a message property or a context property), your message assignment
shape can use:
myMsg(myNamespace.myProperty) = myValue;
Bob is right that you shouldn't need a pipeline here. However, one thing
to watch out for is that doing as bob mentions above won't actually
*promote* the property value, it will only write it into the message
context and, so, it won't be used for message routing, which might be the
problem Guy is facing.
This is a rather non-intuitive issue when using direct-bound ports, but it
can be work around by just making sure that your Orchestration A that
needs to promote the message initializes a correlation set based on the
property you want promoted when it sends the message to the direct-bound
port. This will cause biztalk to correctly promote the property value.
Charles Young mentions some of this in his post on Direct Binding Models:
http://geekswithblogs.net/cyoung/articles/19546.aspx
--
Tomas Restrepo
tomasr@xxxxxxxx
http://www.winterdom.com/
.
- References:
- Direct binding to MsgBox
- From: Guy Derriman
- Re: Direct binding to MsgBox
- From: Tomas Restrepo \(MVP\)
- Direct binding to MsgBox
- Prev by Date: Re: Recieve File in Orchestration Problem
- Next by Date: Dynamic Send Port Auto Creation
- Previous by thread: Re: Direct binding to MsgBox
- Next by thread: RE: Messages left in the messageBox by a fixed orchestration
- Index(es):
Relevant Pages
|