-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DEEP LINKING: deepLinkPath property is using the deepest-level name as path and is not modifiable #217
Comments
@reganwolfrom Can you provide examples. |
@mfriesen Here is an example:
Ideally, this wouldn't show as a file named Also, the contentType is incorrect. |
The plan is to allow path to be modifiable, allowing for file names. |
mfriesen
added a commit
that referenced
this issue
Jul 7, 2024
* 215 - Add "ocrNumberOfPages" to OCR action * #207 - GET /documents/{documentId}/content - NoSuchKeyException * #217 - deepLinkPath property is using the deepest-level name as path and is not modifiable * #218 - POST /search tag range not inclusive of "end" value * #228 - add IDP Mapping * #227 - Modify "Only available with Pro/Enterprise" text in /documents/{id}/ocr endpoints * #226 - Add ability to publish document * Updated console to 3.6.0 * #232 - Add Schema Classification * #231 - Require valid URL on deepLinkPath property * #195 - Users API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For deep links, using the deepest-level name may work in some cases, such as SharePoint (?), but for Google Drive, that name is an ID, rather than a human-readable name.
It isn't essential to retrieve a human-readable name, but ideally, it should be possible to provide a name for the 'path' property.
If it is not workable to do so, it may make sense to create a system attribute or property for this deepLinkName value, which could then be used for display when available.
The text was updated successfully, but these errors were encountered: