%Filename% macro is not replaced with the disk filename

re: %Filename% macro is not replaced with the disk filename

Piers — Mon, 10 Jul 2006 20:55:53 GMT

It seems relatively easy to do this within an orchestration, but I am not so sure how to do this with a custom pipeline. Do you have a custom pipeline example that does this? Thanks.

re: custom pipeline

Adrian Hamza — Tue, 11 Jul 2006 00:29:42 GMT

I don't have a sample but I'm pretty sure you will find at least a few custom pipeline samples outthere if you search on the Internet.

re: %Filename% macro is not replaced with the disk filename

Piers — Tue, 11 Jul 2006 19:40:07 GMT

I admit that I am fairly new to BizTalk, but I did do a search for custom pipelines and found plenty of good examples. But, all the examples deal with one incoming message, IBaseMessage in the Execute method. For what we are trying to do, we need to get the incoming message (diskIncomingMsg), retrieve the filename of that message and replace the outgoing message (sharepointOutgoingMsg) filename.

The way I see to do this with a custom component in a pipeline would be to do the following:

- Use the IPersistPropertyBag.Save method in the receive pipeline to save the diskIncomingMsg filename.

- Use the IPersistPropertyBag.Load to retrieve the diskIncomingMsg filename in the send pipeline

Or, possibly I could promote a property in the custom component in the receive pipeline and save the diskIncomingMsg filename there to be retrieved in the send pipeline?

re: custom pipeline

Adrian Hamza — Wed, 12 Jul 2006 01:45:20 GMT

You have only one message diskIncomingMsg that is modified in the pipeline, you don't have nor do you need two messages. The WSS adapter uses the filename from the WSS.Filename context property. The only thing that you need to do in your receive pipeline, is to modify the diskIncomingMsg and copy the 'filename' value from the FILE.ReceivedFileName to the WSS.Filename context property. When the message exits the pipeline, the filename value will be present in both context properties. You will use IPersistPropertyBag.Load to load the filename value from the FILE.ReceivedFileName context property and then you will use IPersistPropertyBag.Save to save that value in the WSS.Filename property.

re: %Filename% macro is not replaced with the disk filename

svek — Tue, 05 Sep 2006 01:11:10 GMT

How do you use WSS.Filename from a pipeline component?

Don't you have to you use the
Context.Write(_PropertyName, _PropertyNamespace,. sPropertyValue) method?

I haven't been able to find what namespace the WSS-adapter uses. Has anyone else?

re: Namespace used by WSS adapter

Adrian Hamza — Tue, 05 Sep 2006 20:41:44 GMT

You can use BizTalk MMC to discover the namespace and all other details for adapters property schemas and more.

Under BizTalk Group -> Applications -> BizTalk System -> Schemas, you will find the WSS.bts_WindowsSharePointServices_properties XSD schema that defines the WSS adapter namespace and properties.

The property schema namespace for WSS adapter is 'http://schemas.microsoft.com/BizTalk/2006/WindowsSharePointServices-properties'

re: %Filename% macro is not replaced with the disk filename

Onur BIYIK — Mon, 11 Dec 2006 11:30:35 GMT

I have created a simple orchestration to pass filename to wss adapter.

I works ok for most file names. I know, not all NTFS file names are valid for sharepoint. But there are some files which i can upload manually but wss adapter appearently not.

"ShowTv.RingtoneDistributor.DebitProxy[13-15].rar" is not a valid value for the 'Filename' property. Windows SharePoint Services file names can not contain more than one '.' character.

Is this a bug in wss adapter? How can i convert file names to be sharepoint compatible?

re: %Filename% macro is not replaced with the disk filename

Adrian Hamza — Wed, 13 Dec 2006 02:11:45 GMT

It's a known limitation that's documented here http://msdn2.microsoft.com/en-us/library/aa558724.aspx

The design time file name will be expanded at runtime into Windows SharePoint Services file names. This Windows SharePoint Services file name has some additional limitations, which are described as follows:

Valid Windows file names can contain any Unicode characters with the exception of the following: / \ : * ? < > | " # { } % & ~ or tab characters and multiple periods.

The file name cannot be longer than 256 characters and the entire URL must be less than or equal to 256 characters.

If the expanded Windows SharePoint Services file name contains invalid characters, or if the expanded file name or URL is too long, an error will be logged in the application event log and the message will be suspended. The error and the message state will also be visible in Health and Activity Tracking (HAT).

re: %Filename% macro is not replaced with the disk filename

Asif Azad — Mon, 07 Apr 2008 19:31:24 GMT

I have the same problem with the Macro %FileName%.

But the links

( http://msdn.microsoft.com/library/en-us/BTS06Operations/html/1ff50fb8-7ba0-47b8-9476-d57413989346.asp?frame=true )

you gave have been replaced ( or not available ). So please can you give me alternative links ..??

Thanks…

Asif Azad

re: %Filename% macro is not replaced with the disk filename

Adrian Hamza — Mon, 07 Apr 2008 20:10:43 GMT

Try these links:

WSS ADAPTER

http://msdn2.microsoft.com/en-us/library/aa558724.aspx

http://msdn2.microsoft.com/en-us/library/aa547920.aspx

ALL ADAPTERS

http://msdn2.microsoft.com/en-us/library/aa578103.aspx