Hi Everyone, I am using "Appian Document from Base64 String" Sma

siddharthg521 over 11 years ago

Hi Everyone,
I am using "Appian Document from Base64 String" Smart service, that is used to get the attachment from a download link. This smart service has 'docExtension' as one of its input parameter. Now this smart service works fine for pdfs,mp3,doc format. By fine I mean it successfully gets the attachment present on the given download url in Appian.However, if any attachment is of the form '.docx' then it gets the document in appian, but when one tries to access that .docx document in Appian it says that the file can not be opened and is corrupted.

Is there a way where in I can get and access .docx extension file in Appian using this smart service.
This is bit urgent. Any help would be appreciated.

Thanks in advance....

Discussion posts and replies are publicly visible

Parents

0 elizabeth.epstein over 11 years ago

The plugin on Forum is the latest version, and I have not had any problem accessing any specific document types including Word/Excel.

Please verify that your Return Content Type on the Send HTTP Request service is set to Binary rather than Auto or Text. I suspect there is an XML in the content-type response header, which would lead the service to interpret the response as text rather than B64 encoded binary.

If setting it to binary doesn't work, please turn debugging on
(log4j.logger.com.appiancorp.process.runtime.activities.HttpRequestActivityNTLM=DEBUG
log4j.logger.com.appiancorp.util.http=DEBUG)

and post the Application Server output here. From now on please just reply to this thread instead of posting in all the other threads as well. Thank you.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 elizabeth.epstein over 11 years ago

The plugin on Forum is the latest version, and I have not had any problem accessing any specific document types including Word/Excel.

Please verify that your Return Content Type on the Send HTTP Request service is set to Binary rather than Auto or Text. I suspect there is an XML in the content-type response header, which would lead the service to interpret the response as text rather than B64 encoded binary.

If setting it to binary doesn't work, please turn debugging on
(log4j.logger.com.appiancorp.process.runtime.activities.HttpRequestActivityNTLM=DEBUG
log4j.logger.com.appiancorp.util.http=DEBUG)

and post the Application Server output here. From now on please just reply to this thread instead of posting in all the other threads as well. Thank you.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data