When projects are added to the BIMrx® Cloud Manager database they are assigned a File Path local folder location. This location is added/updated in one of two ways:

Please Note—this process not only adds new projects to the database—i.e., those that pre-existed BIMrx® Cloud Manager or were simply not added using it—but can also be used to update existing projects with a different File Path location. 


Files are recognized as “locatable” by the Local Files browser when the Local Folder setting for the project points to a directory location having a sub-directory containing the project’s name. All files to be uploaded for the project are stored in sub-directories using the project-named folder as the top-level root.

In the screen above, the current project local file folder path A is displayed in the tool-tip when the cursor pauses over a project. Please note this is available for all projects, including those without a locatable path.

In the above example, since the selected and checked project was set to “C:\Project Repository\Projects” A, all contents found there are displayed in the center “Local Files / Upload to BIM360” column. At the top of the “Local Files” display for the project it also displays the location B of the assigned local repository and the project-specific sub-directory C containing the actual folders and files displayed. 

Important—As of BIMrx® Cloud Manager Release v2.9.0.2 it is mandatory for the first-level folder path to always be included in the local file folder path D. (Previously it could be excluded and a Program Files upload level was assumed and inserted automatically at the time of upload.) The first-level folder path must be named Project Files and/or Plans—or, if either or both have been renamed on BIM 360®, then these folder(s) must equal those names. If not, the application will produce an error when attempting to upload.

As mentioned above, the local file folder path assigned to the project path always displays in the project tool-tip.

This is useful when troubleshooting issues with files not being available for upload.

The most common cause for files not being found by projects for upload are an inaccurate repository location (in this case simply pointing to the wrong place):

Or erroneously including the project name in the file location path:

As mentioned, this is easily remedied using the Add Existing Projects to Database procedure to change the repository location as described in Browse Projects.