We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
list_folder / get_file_metadata not returning path_lower
Hi,
I am trying the list_folder & get_file_metadata APIs, but both of them doesn't seem to be returning path_lower/path information in FileMetadata. The value is null. I tried from my java code...
In this case, this would be because you're using asAdmin as to administratively access team content on behalf of an admin, who may not necessarily have that content mounted in their account.
To get the path values, you'll need to make the call in a context where the content is mounted, such as by doing any of the following, as applicable/desired:
- use withPathRoot to set the root for the call to somewhere where the content is mounted (e.g., a team space, or a member folder)
- switch to using asMember instead of asAdmin, if the admin does have the content mounted in their account
- switch to using asMember instead of asAdmin and instead specify the member ID for a member that does have the content mounted in their account
Greg-DB
Dropbox Staff
Dropbox StaffIf the path fields aren't set, e.g., in the metadata for an item returned by /2/files/list_folder[/continue] or /2/sharing/get_file_metadata, that indicates that the item isn't "mounted" in the account/root for the call, and so does not have a path to include.
The File Access Guide, Sharing Guide, and Team Files Guide may be useful references.
If you believe this is occurring erroneously, please show us how you're configuring the call so we can take a look. Just be sure to redact the access token.
Thanks. I went through the documentation, still unable to pinpoint the issue. I am calling list folder API using folder id, is that the reason?
ListFolderResult listFolderResult = dbxTeamClient.asAdmin(<ADMINID>)
.files()
.listFolderBuilder(<FOLDER_ID>)
.withRecursive(true)
.start();
- Greg-DB
In this case, this would be because you're using asAdmin as to administratively access team content on behalf of an admin, who may not necessarily have that content mounted in their account.
To get the path values, you'll need to make the call in a context where the content is mounted, such as by doing any of the following, as applicable/desired:
- use withPathRoot to set the root for the call to somewhere where the content is mounted (e.g., a team space, or a member folder)
- switch to using asMember instead of asAdmin, if the admin does have the content mounted in their account
- switch to using asMember instead of asAdmin and instead specify the member ID for a member that does have the content mounted in their account
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
