Uploading Folders & Documents
Drag & Drop
To upload a file or folder, drag it from its current location to the desired directory in buildagil while holding down the mouse button.
Upload via the tab
To upload a file or folder, you can select either "File" or "Folder" in the desired folder within the document view.
You can then select and open the file or folder in the local directory.
File upload, drag-and-drop, document management, upload folders
Uploading a New Version of a Document
To upload a new version of a document, you can upload the file again with the same name to the same folder. This will replace the existing file.
Alternatively, you can drag and drop the new file directly onto the existing file. A prompt will then appear asking whether you want to replace the file with its current name or with the new name.
The new file version is automatically listed in the version history. For more information about the version history, see the following article: Document Version History. If you want to notify people about a new document version, a Information can be created directly from the file’s options.
Document version, replace file, version control, version history, file update, change history, document revision
Syncing with OneDrive
You can sync the document library locally to your computer using Microsoft OneDrive. For more information about OneDrive synchronization, see the following article: OneDrive Synchronization.
Troubleshooting
- Troubleshooting Uploads
- Troubleshooting Automatically Truncated File Names When Saving
- Troubleshooting Inconsistent Modification Dates After Uploading via OneDrive
Troubleshooting Uploads
If an error message appears when uploading files and folders stating that the file path or file name is too long, that the file is currently locked, or that there is a connection problem, this can have various causes. The message may also appear if the path from which the file originates is too long. It’s also possible that file names are automatically truncated.
When uploading files, Microsoft imposes a character limit. If the path (number of characters in the file name plus the names of all folders) from which the file originates (e.g., from a local file storage location) or the destination path in buildagil is longer than 260 characters, the file cannot be uploaded. In this case, the following solutions may help.
- Upload the file to the top level of the folder structure and move it (this does not guarantee version control)
- Move the file to be replaced to a higher-level folder, then overwrite it with the new file, and finally move it back to its original location
- Upload a file from the desktop
- Make folder structures flatter (fewer deep folders and shorter folder names)
In the project settings, you can enable the extended folder name feature to optimize the length of folder names. It is also recommended that you add categories to your documents so they can be found more easily using the search and filter functions.
For detailed information on extended folder names, see the following article: Extended Folder Name.
For detailed information on the categories, see the following article: Categories.
Upload error, path length limit
Troubleshooting Automatically Truncated File Names When Saving
When a file is saved as a copy or in a different file format (e.g., PDF) using the "Save As" option in an app (such as Excel, Word, etc.), the file names may be automatically truncated. This happens when the entire path—that is, the storage location including the filename—is longer than 260 characters. This limit is a system-related restriction imposed by Microsoft, since buildagil’s file storage is based on SharePoint.
Behavior
If the maximum path length of 260 characters is exceeded, the file cannot be saved as expected. Instead, the following may happen:
- The file is saved in a folder higher up in the directory structure that still falls within the 260-character limit
- The file name is truncated so that, together with the path, it does not exceed the character limit
Solutions
- First, save the file in a folder that is not too deep within the folder structure. You can then move the file to the desired location.
- Check whether the folder structure can be simplified to shorten the path
- Use shorter file names
File name is truncated; file name is automatically shortened
Troubleshooting Inconsistent Modification Dates After Uploading via OneDrive
When uploading files to buildagil via OneDrive, the modification date may appear to be in the past even though the creation date is displayed correctly. This behavior occurs because the modification date stored in the metadata is carried over during the upload. In most cases, this affects older file versions. The modification date was stored in the metadata when the file was saved and was carried over during the upload. The creation date was overwritten because buildagil recognized the file as a new version. This behavior is caused by OneDrive and cannot be changed. To prevent the modification date from appearing before the creation date, we recommend uploading the files directly via buildagil.
Updated on: 02/07/2026