Hi,

Firstly, the file name is not random, even if it looks like it. It's what called "Base64 encoded".

Secondly, no, you cannot control which folder each file will be placed in today. Can you explain why you want to control that?

Thanks!
 

Thank you for your update, is there any plan to support multiple folders and readable file name in future release? 

From an IT perspective when using Windows File sharing as repository, this is for ease of backend support and to avoid having a folder with hundreds thousands of files; in our case 7 digits number of files and counting, which can slow down backup/DR restore tasks and increase the latency to retrieve a file when multiple users is trying to write or read from the same folder.

This design was also a request from our Operation/development team which I cannot say why on their behave.

Thanks!

I know there's a request in supporting multiple network/SMB servers/shares but we don't have any details on when that will be implemented. If it will also support pointing out specific folders in a single share/server remains to be seen.

The "unreadable" (it's actually readable if you run it through a Base64-decoder) file names are there for a reason and I would not expect that to change. It's better that you adjust to it or, for that matter, trust that IFS Cloud File Storage will handle the files properly for you.

Do you know for a fact that there's a performance problem with that many files in a folder? I know that in the old days it was a problem but I would suspect file systems and related software to be faster today.

If you can show that the file naming approach and worries about performance are concrete, and not just assumptions, I suggest you file an idea request here on IFS Community (in the Ideas section), or even a support case if you have big problems.