| Author |
Why does file keep naming itself after macro???
|
|
|
| I am able to successfully rename a file in one of my Orchestrations using
the following code:
FileMessage(FILE.ReceivedFileName) = strFileName;
When I try it in another one of my Orchestrations the it only seems to
rename the file after the Macro: %SourceFileName%
The code is the same the send port setup exact same, i must be missing a
setting somewhere, any help is appreciated.
| |
| Stephen W. Thomas 2004-10-26, 5:48 pm |
| Hello.
Are you using a pass through send port on the 2nd message?
Just a thought…
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"aj" wrote:
> I am able to successfully rename a file in one of my Orchestrations using
> the following code:
>
> FileMessage(FILE.ReceivedFileName) = strFileName;
>
> When I try it in another one of my Orchestrations the it only seems to
> rename the file after the Macro: %SourceFileName%
>
> The code is the same the send port setup exact same, i must be missing a
> setting somewhere, any help is appreciated.
>
>
>
| |
|
| no I am using the flat file assembler and need to do so.
"Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
message news:FECABA90-1756-4E29-B902-33853438DC69@microsoft.com...[vbcol=seagreen]
> Hello.
>
> Are you using a pass through send port on the 2nd message?
> Just a thought.
>
> Stephen W. Thomas
> http://www.geekswithblogs.net/sthomas
>
>
> "aj" wrote:
>
using[vbcol=seagreen]
| |
| Stephen W. Thomas 2004-10-26, 5:48 pm |
| Now that I think about it more, I do not think that the ReceivedFileName
Property filters through to the Send Pipeline (i.e. you can not set that
property and have your output named that). I think for this you need to use
a dynamic port to set the sending file name.
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"aj" wrote:
> no I am using the flat file assembler and need to do so.
>
>
>
> "Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
> message news:FECABA90-1756-4E29-B902-33853438DC69@microsoft.com...
> using
>
>
>
| |
| James Longstreet 2004-10-29, 7:46 am |
| If your incoming adapter is not file, I don't believe what you have is going
to work correctly.
thanks
"aj" wrote:
> I am able to successfully rename a file in one of my Orchestrations using
> the following code:
>
> FileMessage(FILE.ReceivedFileName) = strFileName;
>
> When I try it in another one of my Orchestrations the it only seems to
> rename the file after the Macro: %SourceFileName%
>
> The code is the same the send port setup exact same, i must be missing a
> setting somewhere, any help is appreciated.
>
>
>
| |
| Greg Forsythe 2004-10-29, 5:49 pm |
| The FILE.ReceivedFileName is a message context property.
It can be set inside the orchestration on any message and will follow that
message where ever it goes.
The key is setting it on the right message.
You have to set the FILE.ReceivedFileName on the message that is being sent
not the message that was received, these may be different.
e.g if you use a transform in an orchestration
filemessage -> transform -> transformedmessage->send port
transformedmessage(FILE.ReceivedFileName) = strFileName;
Greg
"aj" <aj@nospam.com> wrote in message
news:%23Iz5CL2uEHA.2520@TK2MSFTNGP15.phx.gbl...
> I am able to successfully rename a file in one of my Orchestrations using
> the following code:
>
> FileMessage(FILE.ReceivedFileName) = strFileName;
>
> When I try it in another one of my Orchestrations the it only seems to
> rename the file after the Macro: %SourceFileName%
>
> The code is the same the send port setup exact same, i must be missing a
> setting somewhere, any help is appreciated.
>
>
|
|
|
|