We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
To use properties/update, am I required to first do properties/add first?
In order to use properties/update, am I required to first do properties/add on a file? Reading your description for the "update", it seems it should "Add, update or remove properties associated" wit...
Hm..🤔 toki4004, Let's imagine you're famous painter. 😉 You have expositions in many galeries (think for the galeries as files). You may expose not only completely ready pictures, but also some drafts (count all pictures and drafts as properties). Of course from time to time you may update your drafts - add a flower, for instance (the same like properties update). Let's start thinking... would it be possible for you to update some draft that doesn't exist yet; never got started be painted at all (the same like a property not added yet)? 🧐... 😯😀
Hope this gives direction... of thinking.
Hm..🤔 toki4004, Let's imagine you're famous painter. 😉 You have expositions in many galeries (think for the galeries as files). You may expose not only completely ready pictures, but also some drafts (count all pictures and drafts as properties). Of course from time to time you may update your drafts - add a flower, for instance (the same like properties update). Let's start thinking... would it be possible for you to update some draft that doesn't exist yet; never got started be painted at all (the same like a property not added yet)? 🧐... 😯😀
Hope this gives direction... of thinking.
Ok, that's what I thought. The description language implies that the property would be added if it doesn't exist - the way I read it.
toki4004 wrote:... The description language implies that the property would be added if it doesn't exist - the way I read it.
Hi again toki4004,
Yes, you are correct - it implies so. You have just hit a big Dropbox pain - the documentation!!! It's not just about the documentation actually - here some conceptual design bugs bring up (and followup implementation mistakes).
Usually when something is going to be added: if missing - would be just added, if existing - may be error or may be updated/overwritten. Here, Ok - if exists, error is assumed to be (in spite in file upload is assumed to be update). On other side when there is explicit method to update/overwrite something, it usually mean exactly update or overwrite and nothing more (a good idea would be if you try any other operation to result in error). Here, by design is just opposite (usually assumed as error, in spite not mandatory) and implemented correct (probably by mistake 😁 - example of a good mistake).
There is one more... inconsistency: That what you're looking for may be found in /2/file_properties/properties/overwrite. It's not mentioned, but here when particular property is missing (property group actually), it's gonna be created. It's not certain that such behavior matches design, but is implemented so (usually assumed as bad practice 🤷). Whatever it's assumed as, it's so... The only clear thing is that documentation doesn't match to the actual endpoints behavior (no completely, at least).
Hope this adds some piece of extra clarity.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
