02-18-06 03:51 AM
Hi Venkat,
The result based on your setup is expected. The easiest way is retify your
issue to separate this into two orchestrations: one for initial processing
and the next for update.
Once you have got the simpler setup working, you can try the more difficult
ones.
If you really want to use the same orchestration for creation and update,
by calling it twice, you would need some logic in the orchestration to
control the flow. And to ensure that there is no duplicate of same
activity records, you would need to start this activity in the port
(receive pipeline) and resume it to the orchestration and then it can call
itself again for update.
Please let me know if this helps.
Thanks,
Keith Lim [MSFT]
--------------------[vbcol=seagreen]
22:12:30 GMT)[vbcol=seagreen]
CLR 1.1. 4322),gzip(gfe),gzip(gfe)[vbcol=seagreen
]
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!transit3.readnews.com!
news-out.readnews.com!postnews.google.com!g47g2000cwa.googlegroups.com!not-f
or-mail[vbcol=seagreen]
Thanks,
Keith Lim [MSFT]
My BizTalk BAM Blog: http://blogs.msdn.com/keithlim/default.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
[ Post a follow-up to this message ]
|