Vault File Structure
Where can I see how this file upload structure came to be?
C:\Aras\Vault\YOUR_DB_NAME\FIRST_CHARACTER_OF_ID\SECOND_AND_THIRD_CHARACTERS_OF_ID\REST_OF_ID\FILE_NAME
Forum Discussion
Hello,
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.
Chris
Hi Christopher, thanks a lot for your response. Is there any way to determine if the uploaded "file" to the vault was a directory or folder? Because the vault already uploads folders as files, even though they are not.
Hello,
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?
Chris
Hi,
Ah no, not a zip file. A folder. So basically here are the steps to reproduce the issue:
- Create a new Document item
- Open a separate windows explorer, and browse into your files/folders
- Drag and drop a folder into the Files tab
- Fill out necessary fields, then save the Document item.
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
