Where can I see how this file upload structure came to be?
This folder structure works to improve performance by keeping the number of files and folders inside of a single directory to a minimum. This is especially important as we expect our users to store large numbers of files inside of Aras Innovator.
I believe the code for the vault that handles building this structure and looking up files using this structure is stored inside of a DLL, so it's not accessible to see or change.
It's not possible to upload a folder as a File item. Are you referring to a compressed format like a Zip file?
I'd also like to say as a general note, you should never need to manually access the Vault. Could you elaborate on what your use case for this is?
Ah no, not a zip file. A folder. So basically here are the steps to reproduce the issue:
The created Document item saves the dragged folder as a file type. Even though it is in its entity a directory/folder. Our clients would like to prevent this from doing so, as it is in a way, taking up space on the tool. That's why I'm trying to learn from different angles, in a way, also learning how the tool behaves on certain parts.
We have initially tried writing a method which loops all the extensions registered as a file type of the File item, then checks if the D&D file is legitimately a file (or with extension). It worked... for a moment, because a test case appeared on what if you D&D a folder/directory with this name: ex. folder.docx
The File item actually read this as a legitimate .docx file when actually it's a folder. So, our initial JS method became useless. Hope I'm making sense here
Folders are not able to be uploaded to Aras Innovator. If you use your same steps but use the "Create New" button instead of dragging the file in, you'll see that you aren't able to select a folder from the dialog that pops up. You can also see if you check either the File item in the database of the file created in the Vault that even if you drag the folder in to create the file item, it is saved as an empty, extension-less file and not a real folder.
Thank you for pointing this out. I've filed this as an issue internally. In the meantime, you can inform your users that folders are not intended to be added directly, or you can point them to using the "Create New" functionality of the Client.
I just installed the 12.0 instance, and tested it. However, I still was able to save the Document, despite the dragged folder. Did I miss something?