adm_my_documents_v
One row per active document the ADM user established in the current session may see, with the metadata of its current version.
Overview
Section titled “Overview”Group: Application integration
Category: Documents - Core document analysis and reporting
Use Cases
Section titled “Use Cases”- The document report in your own application
- Joining your business records to ADM documents by document_id
- A folder listing filtered by folder_id or folder_path
Columns
Section titled “Columns”The view contains 19 columns providing comprehensive information:
| Column Name | Description |
|---|---|
document_id | Primary key of the document. Anchor customer relationships on this, not on a name or a path, because those can change. |
document_name | Name of the document, including its extension. May contain spaces. Not unique on its own - only unique within a folder among active documents. |
folder_id | Primary key of the folder holding the document. Joins to adm_my_folders_v.folder_id. |
folder_path | Full lowercase path of the containing folder, without a trailing slash. A display and lookup convenience; it changes when a folder is renamed or moved. |
document_path | folder_path and document_name joined with a slash. A convenience, not an identifier. |
file_mime_type | MIME type of the document, as corrected from the file content on upload. |
latest_version_id | Primary key of the current version. Joins to adm_my_document_versions_v.version_id. Null only for a document whose version row was never created. |
latest_version_number | Version number of the current version, counting from 1. |
latest_file_size | Size of the current version in bytes, raw. Format it in your own application. |
latest_version_created_date | Timestamp the current version was uploaded, i.e. when the file content last changed. |
latest_version_created_by | User who uploaded the current version. |
legal_hold_flag | Y if the document is on legal hold. Independent of every other state: a document on legal hold is an ordinary, readable document that the delete APIs refuse. |
user_owner | Uppercase username owning the document, i.e. it lives under /users/ |
group_owner | Uppercase group folder name owning the document, i.e. it lives under /groups/ |
owner_type | USER, GROUP or NONE, derived from user_owner and group_owner. |
created_date | Timestamp the document was created. |
created_by | User who created the document. |
updated_date | Timestamp the document row was last written. A new version, a rename, a move and a lifecycle change all touch it, so it is NOT a complete change feed - a new tag, comment, annotation or share does not move it. |
updated_by | User who last wrote the document row. |
Key Features
Section titled “Key Features”- Unique by document_id, whatever route grants the access
- Identity from the ADM context - no username parameter to spoof
- Current-version metadata already joined
- Raw sizes and timestamps, formatted by the caller
Related Views
Section titled “Related Views”Other views in the Documents category: