Yep, reading my old blog!
Yes, there are many ways you could implement it. Good luck.
Eric
http://blog.biztalk-info.com
"stuforman" <stuforman@[EMAIL PROTECTED]
> wrote in message
news:1185825595.840676.313890@[EMAIL PROTECTED]
> On Jul 30, 3:19 pm, "Eric Stott" <ericst...@[EMAIL PROTECTED]
> wrote:
>> If you are looking to use the pipeline component (which I don't
>> recommend)
>> you would treat it like any other send pipline.
>> If you are going to use the adapter, you can't use this funtionaility
at
>> all.
>> I have written about how you can create a custom filename that does not
>> adhere to the # filenaming convention
>>
here:http://blog.biztalk-info.com/archive/2006/06/14/Custom_Names_for_the_...
>> Erichttp://blog.biztalk-info.com
>>
>> "stuforman" <stufor...@[EMAIL PROTECTED]
> wrote in message
>>
>> news:1185819876.321125.266630@[EMAIL PROTECTED]
>>
>>
>>
>> >I have a send ****t, with destination folder: d:\hipaa\834out\ and I
>> > want the filename to be something like out_%SourceFileName%. I have a
>> > custom send pipeline that has a flat file assembler. How can I pass
>> > the filename to the ****t? I would think I'm not the first one asking
>> > something like this, but I'm not finding exactly what I need and am
>> > hoping for help. I see that the conext property needs to have the
>> > filename value. How do I go around to do this?
>>
>> > Thank you, Stu- Hide quoted text -
>>
>> - Show quoted text -
>
> thanks Eric, I do have this printed out already (from
> Stottcreations.com). I've have been thinking that it would make sense
> to do everything in one orchestration and just do an if/then statement
> for each type of file. From what I'm reading is that the key is to add
> this component to the orchestration. This sounds like its giving me
> one more reason...
>
> Stu
>
|
