- Newest
- Most votes
- Most comments
May you please confirm that your Lambda function is able to upload the preprocessed file to S3? If not, may you please share the error that you are getting when you try to upload the document to S3.
I was able to resolve the issue described below.
After doing few checks with the Workdocs response that I got in the code I got to know it was the issue there and after changing the parameter for Object type in the code to "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet" I was able to get the file in workdocs as Excel readable and I resolved the issue.
The main issue was previously for the file uploaded in s3 the workdocs automatically took object type as the above shared but when it was coming from the previous lambda it was getting the object type as binary which was sending the file to workdocs as binary. Just chnaging the object type to hardcoded helped me.
I am glad to know that you managed to find the cause of the issue and it is resolved.
Relevant content
- asked a year ago
- asked 3 years ago
- asked 3 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
I dont get any error. The file gets perfectly uploaded to the s3. Also from s3 it goes to Workdocs without any error and finally in Workdocs when I am expecting the .xlsx file to be Microsoft readable it doesnt work.