Issues using HTTP file download Smart service

Hi Nick,

I guess there are some restrictions set in admin console to allow specific type of files into Appian system. Please access the site admin page - /suite/admin/page/file-upload and check.

Hope this helps.

Thanks

Hi Naveen,
Thanks for the reply, currently I am able to get the file downloaded to Appian (documents) folder. But the thing is it's not displaying it's file extension type (preferably .doc & .pdf). So my question was generally when you use the HTTP download/Upload smart services what things might corrupt the files transferred.

Thanks,
Nick

Hi NIck,

Thanks for the clarification. So, I understand that the file is able to download into the Appian folder but the file extension is missing. And Sorry, I'm not quite sure why the file is getting corrupted and chances of corruption. You may try debugging the issue in the following steps.

1. Can you try downloading the file from Appian folder and check whether it is keeping the file format as expected?
2. Can you double check whether file retains the file format at the source location before it is pulling into Appian via this plugin?
3. If above both are positive then we may need to doubt the plugin functionality.

Good luck, Thanks

Hey Naveen,
Thanks again for your inputs, based on your steps you suggested, just to clarify more have more than 100 files of both pdf and doc file, but in some cases there's a whole column or at least three files in repetitive missing their extensions, when I say corrupt I mean in the our case particularly: endpoint doesn't have a file name and extension it will be something like http://url/attached?fileid=1, so the file is being downloaded but in some instances as I said earlier I don't see the extensions.

Regards,
Nick

Hi tongyangn0002 few things here to consider:

1. In case of file download: I believe you are trying to download the file from a third party system, hence first of all you need to communicate with them, whether the file is Corrupted or without its extension at their end, because we have face these issues with SharePoint several times, if so then nothing to do from Appian end, in fact the service provider must update their service. Also are you facing this issues with each and every document download? If not, that means all god from your end. Also can you please specify list of formats which gets corrupted/ didn't transfer properly in your case.

2. Document upload: When you upload a file from Appian KC to third party system using this OOTB smart service, you have to define the extension of the file which you can retrieve using document() , and append it with filename(.) extension, if you don't do so, this file will be transferred without its extension to the target system.

Thanks Alok for your reply, I guess it is the sharepoint thing. I'll look into it, and yes only a few files have this issue rest it looks as normal.

use file name with extension
="testDoc"&".pdf"
or ="testDoc"&".doc"

you will get the uploaded file with given extension

Hi Nick,
why cant you use integration object instead of http file download

Hi Pradeep

Seems like, the are some confusion over this discussion thread, integration object and http file download smart service is meant for two different purposes.

Integration object is meant for: Invoking a service and can exchange the data in form of text ( json, XML etc..) only, which means, we don't have the opportunity to exchange the binary content such as document. Also this can be used to perform authentication operation and return the response of a service.

Whereas Http file download smart service is meant for: downloading a file from an external system into Appian using binary stream.

Also, out if interest, seems like it's a very old discussion thread re-initiated once again :)

Hope this helps.