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
Id given back in delete event
Can I make a feature request? I would be great if the delete events coming back from `/list_folder(/continue)` include the id of the thing deleted. Seems a bit odd that they dont alredy.
Curre...
- Thanks for the post! I can't make any promises, but I'm sending this feature request along to the team.
Greg-DB
Dropbox Staff
Dropbox StaffThanks for the post! I can't make any promises, but I'm sending this feature request along to the team.
how would I know if the team accepts or declines this request?
Its now 2023, and the list_folder api call is still broken (in my mind) regarding 'deleted' files!
Here's the problem.
Simple App that responds to change notices:
With User:
Get Cursor
While deltapages (on cursor):
if .tag = 'file' record info in db (path, and most importantly unique ID as supplied by list_folder)
if .tag = 'deleted' update record in db for given data supplied (list_folder only provides 'path', it DOES NOT provide the ID)
So now only way to look up info in our database is via path on deletes. Which of course you can have duplicate file names in any given folder, each with its own objID. Deleting files fails when using the dropbox API, only way to use it is tell customer to not create duplicate filenames in any given folder (dumb)!
Dropbox please add 'id' to your list_folder call for any .tag = 'deleted' files!!!
thanks! It seems to be that list_folder likely depends on metadata call, which I think is the real culprit (of not giving back the objID on deleted files).
My delete methods now do the hard thing, namely on delete of a file in a given path, list all files in that path that are not deleted, and remove any files from our DB that are NOT listed. That way our DB stays in sync on what is actually happening. Bad news, too many API calls, takes too long for what should be really simple. But it solves the immediate problem (hope I don't hit the rate limiting....)
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
