I am sending a message using the file transport type to a folder. The messag
e is of type xml.xmldocument. I.E there is no schema associated with this me
ssage.

What property can i use for correlation on this message?
The file that is created is picked up again later in the same orchestration 
on a file receive port.

As i mentioned before, the outgoing message is not based on a schema.

Help please??

[ Post a follow-up to this message ]

The question is not yet technical,
business wise - what can you use for correlation?
Is it the filename? is it the root node? is it some other element in the
XML?
what value can you use for correlation in you scenario?

Yossi Dahan
"Mangi" <Mangi@discussions.microsoft.com> wrote in message
news:35B60985-7F2A-4B49-9EAF-11B9161F0FC3@microsoft.com...
> I am sending a message using the file transport type to a folder. The
message is of type xml.xmldocument. I.E there is no schema associated with
this message.
>
> What property can i use for correlation on this message?
> The file that is created is picked up again later in the same
orchestration on a file receive port.
>
> As i mentioned before, the outgoing message is not based on a schema.
>
> Help please??

[ Post a follow-up to this message ]

Spot on Yossi.

I found a workaround yesterday.
I needed to correlate on a value inside the xml document.....OrderID.
Here's what i did.

create a new multi type message with a message type of a schema that conform
s to the incoming xml.xmldocument. I then used the message issign shape and 
the transformation shape with a map. I promoted OrderID on the schema that i
 created and made it distin
guished that made it available for correlation....... It's a really hairy lo
oking orchestration, but it works like a charm.

[ Post a follow-up to this message ]

Is there a reason you cant just use the schema in the receive pipeline to
receive the xml already with the promoted properties?


"Mangi" <Mangi@discussions.microsoft.com> wrote in message
news:4BEFA33A-D8B1-4F3F-81C9-8DA349EC7951@microsoft.com...
> Spot on Yossi.
>
> I found a workaround yesterday.
> I needed to correlate on a value inside the xml document.....OrderID.
> Here's what i did.
>
> create a new multi type message with a message type of a schema that
conforms to the incoming xml.xmldocument. I then used the message issign
shape and the transformation shape with a map. I promoted OrderID on the
schema that i created and made it distinguished that made it available for
correlation....... It's a really hairy looking orchestration, but it works
like a charm.

[ Post a follow-up to this message ]

Oh Snap!!!!!

I never thought of that!
You just started my weekend on a high note, I'll try that right now......



"Yossi Dahan" wrote:

> Is there a reason you cant just use the schema in the receive pipeline to
> receive the xml already with the promoted properties?
>
>
> "Mangi" <Mangi@discussions.microsoft.com> wrote in message
> news:4BEFA33A-D8B1-4F3F-81C9-8DA349EC7951@microsoft.com... 
> conforms to the incoming xml.xmldocument. I then used the message issign
> shape and the transformation shape with a map. I promoted OrderID on the
> schema that i created and made it distinguished that made it available for
> correlation....... It's a really hairy looking orchestration, but it works
> like a charm.
>
>
>

[ Post a follow-up to this message ]