Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
2 file_ids are pointing to same file
"id:sQ8JqHEl8OkAAAAAAAIbNQ" and "id:sQ8JqHEl8OkAAAAAAAIbSg" both point to the same file. I received file_delete event with "id:sQ8JqHEl8OkAAAAAAAIbSg" and received file_download event for same file w...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThanks for your patience while I checked on this for you. While file IDs uniquely identify files, i.e., every file ID identifies a file, and no two files share a file ID, it is possible for two different file IDs to essentially "point" to a single file.
It looks like that's what's happening here. Because of the sharing, unsharing, and restoring operations you performed, you received multiple file IDs over time, but there is only one latest/active instance of the file now. So, querying for either the past file ID or the current one points to the latest active instance of the file.
Thanks for you response Greg,
We (Vera Security) have integration with Dropbox and use the IDs to uniquely identify the file in our system. We listens to the DB events, use the ID to find the file in our system and then perform the corresponding action.
Now if the ID is changed then we cannot find the corresponding file in our system and it breaks the integration.
Can you help us better understand what exactly causes the new ID creation? I have tried sharing, unsharing, delete / restore but I am unable to reproduce it again.
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
