Originally posted by Nick Heppleston at: http://www.modhul.com/2009/03/04/ftp-adapter-context-property-oddities/
Interesting to see that the FTP adapter doesn’t capture the full Uri of the file in its ReceivedFileName context property – instead it simply gives us the filename:
Compare this with the FILE adapter where the full name (incl. the path) of the file is provided:
So, if you need to capture say the folder structure of the FTP server, you need to do a few lines of magic to extract the folder name from the InboundTransportLocation property (shown in green in the first screenshot) and munge it with the ReceivedFileName.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=e45d75b8-7131-4b52-9e38-a64330f2f7d1)
Another one is that it uses the ReceivedFileName property of http://schemas.microsoft.com/BizTalk/2003/file-properties instead of its ft-properties counterpart on a send port when you set the %SourceFileName% macro…