I have a file location object. I am modifying a job, which uses a basic FTP script from a batch script:
- ftp
- open hostname
- username
- pw
- get remoteName localName
When I run this I am able to retrieve the file correctly from the FTP server in plaintext ascii.
However after adding the above configuration into a File Location Object, I am running into problems. I am able to retrieve the file. However, when I analyze the file in WordPad I see that it has been converted into a different format.
It seems like data services is running ftp using the binary method of transport (not ascii). When I manually retrieve the file using this option, I get the exact same file as retrieved by BODS. When opening it it is also appears to be garbage characters (encoded probably?). When using ascii for transfer mode I see my data as expected when viewing as text.
I do not see any option anywhere to change this within Designer.
How can I resolve this? Can I modify the FTP use in a File Location Object to use the ascii method of transfer somehow? Or is there a specific type of file encoding I should be using for my flat files in Data Services - currently I am using <default> as this has worked with the text, does this need to change?
I am using Data Services 4.2.5 without any patches.