| Scott Colestock 2005-08-02, 6:02 pm |
| Another approach on the receive side is to stuff all the "extra" values into
a dynamically generated message (think xmlDoc.LoadXml("...."))
Then you can feed that message as an additional input into your transform.
Scott Colestock
www.traceofthought.net
"Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
message news:8C527FBD-6B07-46F0-A4B9-8ECEC62EAA68@microsoft.com...[vbcol=seagreen]
> Hello.
>
> I don't really follow what you are trying to accomplish 100%. But,
> getting
> the received file name inside a map is difficult. On the Send Port, you
> should be able to use basic Property Demotion to demote the value from of
> the
> message context into a field
> (http://www.biztalkgurus.com/Samples...n-Pipeline.html).
>
> On the receive side, I think your best bet would be to write a custom
> pipeline component to put the value into an attribute on your inbound
> message. Then, you can access it inside the map on the receive port. I
> have
> used a simulate approach to get context values with Orchestation mapping.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.biztalkgurus.com
>
>
> "William" wrote:
>
|