Options for project naming in folder structure

[Brett_B]

In Procore Sync we have the option to either use the Company Name, Job Number, Job Name or a mix of any of the three for each project’s folder name. To prevent long file name issues we would select only the job number because some of our job names are long due to multiple locations.

In testing ODrive are are having issues with long filenames even with the Windows Long File Names option turned on by Group Policy because of the job name adding to the path limitation.

It would be a nice feature to be able to reference the project by only the job number in the folder structure to help reduce these issues like we could in Procore Sync.

[Tony]

Hi @Brett_B,
Thanks for the suggestion. I know this type of advanced feature is being considered.

In the meantime, it is possible to significantly reduce the overall path length using the “sync to odrive” feature. It is not a perfect solution, but it could be useful. Take a look at this post for more information:

Character limit

Thanks for the response @gsvanas! I had actually attempted to work with Bluebeam to address this a few months ago, after doing a bunch of testing. Unfortunately I wasn’t able to get any traction and pretty much ended up where you did with them. To help combat path-related issues with other apps (or Windows, itself), you can use the “sync to odrive” functionality to “short-cut” the path to your projects folder, or to specific project folders. Here is an example of how to do that for the projec…