Documents uploaded with a folder path will download with their full folder path for a filename #185
Comments
mfriesen
added a commit
that referenced
this issue
Jan 22, 2024
New Feature #182 - Document Retry - documents that fail to process are added to a queue for reprocessing #192 - Added POST /documents/{documentId}/actions/retry for retrying of failed document actions #196 - Added OCR support for PDF Portfolio files #194 - Added support for document content to be a "deep link" #189 - Added document "soft delete" #146 - Added insertedDate, completedDate to Document actions #171 - Added Document Workflows #179 - Added Cognito group that allows authentication but no authorization #170 - Added Notification action #168 - Added SMTP support to /configuration API #169 - Added /groups API #201 - Added version of FormKiQ that can be run via Docker Updates #166 - AWS Lambda end of support for Custom Runtime based on Amazon Linux 1 #188 - Intelligent document processing with OpenAI, uses Schemas to improve results #119 - improved performance when removing documents Bugs Fixes #172 - Fixed Fulltext action ending up in a bad state #185 - Fixed GET /documents/{documentId}/url returns full path of document instead of filename #197 - POST /documents/compress is not available for users with READ ONLY access
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I used the sync CLI to upload a number of files from a folder using the
--recursiveflag. These files were therefore uploaded with their folder paths intact, which is great.However, when using the
GET /documents/{documentId}/urlAPI to retrieve a download URL, the signed URL that comes back specifies the full file path in thefilenameportion of theresponse-content-dispositionquery param, e.g.response-content-disposition=attachment; filename="Folder 1/Subfolder A/My File.pdf". This results in the filename beingFolder 1_Subfolder A_My File.pdfwhen you download it.The text was updated successfully, but these errors were encountered: