You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Team Space vs Updated Team Space
Hi, according to this post , all kind of accounts will be migrated to "Updated Team Space" by 2024/01/31. I have a few questions about the migration and APIs behaviour changed. 1) As my observat...
1) The API response is correct. In a non-updated team space configuration, as far as how the API works, the folders in the team space are technically shared folders not team folders.
2) No, unfortunately the API doesn't offer a way to filter out the member folders, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.
Hi Greg-DB , thanks for your quick and detailed reply!
And I have some following questions as well.
1) For old "Team Space" type, does that mean there is only one Team Folder available when calling list team folders API ? (Because we have no account of Team Space type to test, thus we can't get to know the actual result of upstream API), if so, do all other team folders will be located under the first layer when listing the team space by calling list_folder API ?
e.g.
Team Space Root
- Member folder 1
- member folder 2
- team folder 1
- team folder 2
2) We understand we can tell the account type through get_values API, but we want to know if there is a specific event we can get from get_events API for the happening of the migration?
3) Is there any way we can apply a testing Team Space account ?
Thanks for your help!
Greg-DB
Dropbox Staff
Dropbox Staff1) Yes, for the non-updated team space configuration, /2/team/team_folder/list would only return the one team workspace team folder, and that folder contains everything else.
2) While there may be some events related to the migration, I don't believe we guarantee any particular event to use for programmatically identifying it. The feature values are the supported way of checking the configuration. Is there some reason you need to check this in the event log? I'll be happy to pass along any feedback.
3) Yes, you can request a Dropbox Business Development Account by following the instructions under "" here: https://www.dropbox.com/developers/support . Be sure to be specific and indicate what kind of team configuration you need.
Hi Greg-DB thanks for your reply.
Greg-DB wrote:1) Yes, for the non-updated team space configuration, /2/team/team_folder/list would only return the one team workspace team folder, and that folder contains everything else.
So I can assume there should be other team folders existed under this root team space workplace, is that correct?
2) While there may be some events related to the migration, I don't believe we guarantee any particular event to use for programmatically identifying it. The feature values are the supported way of checking the configuration. Is there some reason you need to check this in the event log? I'll be happy to pass along any feedback.
The purpose we need to be aware of the change is because the folder structure is a bit different and will affect our traversal flow. That's why we need to know once the migration happened just in case.
3) Yes, you can request a Dropbox Business Development Account by following the instructions under "How do I test my application?" here: https://www.dropbox.com/developers/support . Be sure to be specific and indicate what kind of team configuration you need.
Yes, we've apply a testing account via this google form and that one is in Updated Team Space. I will request for another one of Team Space then test to see how it goes.
Thanks for those useful information.!
- Greg-DB
1) Any given team may or may not actually have additional folders created at any particular location at any given time, so I do not recommend making assumptions about the existence of items. Apps should use the API to check to see if particular items exist or not.
2) Thanks for the note. Attempting to use the log may be more difficult and less efficient though, so the recommendation is to use the feature endpoints to check whenever needed.
3) I see your request was received and should be processed soon.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
