Child Item

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.

Current:

{
".tag": "deleted",
"name": "General_Engingeering_Test_Project.pdf",
"path_lower": "/h22/h2/general_engingeering_test_project.pdf",
"path_display": "/h22/h2/General_Engingeering_Test_Project.pdf"
}

Want:

{
".tag": "deleted",
"id": "id:JOP3N_6VLJAAAAAAAAAJ-A", <- notice there is an id now
"name": "General_Engingeering_Test_Project.pdf",
"path_lower": "/h22/h2/general_engingeering_test_project.pdf",
"path_display": "/h22/h2/General_Engingeering_Test_Project.pdf"
}

thanks

ps. i can see how it would be unfair to make comparisons across services but i just wanted to point out that both google drive and box return an id in their delete events.

Find more posts tagged with

API

Abuse

Accepted answers

Greg-DB

Thanks for the post! I can't make any promises, but I'm sending this feature request along to the team.

All comments

Greg-DB

Thanks for the post! I can't make any promises, but I'm sending this feature request along to the team.

YawHide

how would I know if the team accepts or declines this request?

Greg-DB

I'll make a note to follow up on this thread if/when I have an update for you.

YawHide

@Greg-DB wrote:
I'll make a note to follow up on this thread if/when I have an update for you.

thanks again

quandt

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!!!

Greg-DB

@quandt Thanks for the feedback! I'll pass this along to the team.

quandt

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....)