Make file prefixing an option - file requests

Create toggle feature like "Dropbox system extension" in settings:   turns off appending Dropbox owner name to files shared with other DB account holders.   

This is quite an important feature for us, please!

Another vote for disabling file renaming. At least off the option to disable renaming when creating the request.

Like others here, I use this feature to accept inputs from collaborators and the files I receive are expected to have specific names to automatically integrate in my image editing workflow.

This is pretty ridiculous that it's not an option. Come on Dropbox, just give us an option to turn off the file renaming, it can't be that difficult to do. If someone happens to upload a file where another similarly named one has already been uploaded, then it just needs to append a (1) or something like that to the end, as happens when you download the same named file to your computer from a website. 

Ideally, we'd be able to customise the file naming, if we want to have certain things added to the files, but I understand that that would take much more time to code in, so at the least give us the option to turn it off. 

Thanks!

Hi,

Another vote for not renaming the files at all. Please add the option to disable renaming at least!

Having the same issue, crazy this thread/request is 5 years old! Come on Dropbox, simple function that has many like me discontinuing service. 

Bump - please add a feature to be able to choose disabling prefixing the uploader name to any uploaded files through a file request.

I definitely appreciate being able to audit/track who has uploaded files some of the time. However, coming from a media/production company there are so many cases where simply receiving the files without any name change would save a huge amount of time instead of having to rename - when you're working with large volumes of files it really makes a huge difference not having to do batch renames every time! If I still need to audit who was responsible for an upload then I can check the admin console anyway.

Thank you.

Just opened an account with Mega as a previous commenter suggested, and can confirm that there's no auto renaming of files. I use the file request feature heavily so I'll be switching away from Dropbox today. 

It is such a lack of basic understanding from Dropbox team! They are so stuburn and clueless what we want. Product should be developed from customers perspective, not from what ever your engineers or product owners came up and their lack of capability to understand a bigger majority has to be pain for everyone. Why?! Absurd.

If I upload file, I don't want it to be modified! And there is nothing else to discuss here! but no, wait, Dropbox team is explaining how we supposed to want to use it, in pain and frustration, and again.. why? ..well, because they do see excuse to spend money and time to improve it, or rather fix underlying problem!

And the funny thing is, when Dropbox team gives such silly response "we can't do that now", all the rest of industry is laughing, because it can easily be done, when you want. So it's just a politely brushing all the heat into sink and flushing it down.

If your engineers can't do it, hire the ones which can, and there is plenty of them capable of making all of those improvements and missing features on Dropbox, seriously.

If I ask some one to upload photo of me, that they took, it's is very obvious I don't want other persons name on photo of me. That is so silly, that any responsible employee would say "NO" to this. My guess is that Dropbox either has an underlying technical debt problem, that is blocking them do things the right way, or maybe just poor managers, or even chiefs.

If file with same name is already uploaded, very basic thing to do, is to add an incremental number at the end of file. It's supper old solution. Do you have just junior engineers working at Dropbox?

At least make option should File Upload feature require or not some prefix for file name. It me, the requester, sets this as required, then require with clear intention why. Now, it's unclear to anybody, and in result creates even bigger frustration to everybody. Everybody! This would be no brainer issue to any self-respected team to spot it and solve it, and would be embarrassed and want to resolve it even more, if clients keeps complaining as they do here! Also, prefix, not required in most of the cases.. and yet, you decide it will be and you force everyone to obey your aggressive attitude towards providing poor product experience and ignoring customer needs.

How can this still not be an option?

We work with loads of video files from customers witch are synced to various media servers, this affects the whole workflow and makes "file request" unusable so we need other applications for that. 

Convince me why we should stay with the Business Advanced Plan?

Thank you for your idea, while we can’t take every idea forward we do regularly re-review and will update you if anything changes!