File downloads are named using the document ID rather than the original filename #48
Milestone
Comments
mfriesen
added a commit
that referenced
this issue
Sep 25, 2022
* #44 - DELETE Document API does not work unless a corresponding file exists in S3 * #40 - Add last modified to GET documents and GET document/{id} * #45 - Metadata records with no corresponding S3 object are causing issues on GET /documents * #46 - 500 Error in /search endpoint when using large "limit" with "responseFields" * #48 - File downloads are named using the document ID rather than the original filename * added POST /documents/{documentId}/actions * POST /searchFulltext - added pagination
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you use the content url that results from the Get Document Content or Get Document URL endpoints to download the file, the filename will always be the GUID representing the document ID. There doesn't seem to be a good way to force the downloaded file's name to match the original "path" or filename parameter.
The text was updated successfully, but these errors were encountered: