Automation to open Revit File - File.Path From Bimbeats

General
1

I am wondering if anyone knows how I can get the ACC revit file - File path that external Automation could use to know what file to open. The guy doing the automation for me is telling me that the current value given for File path (“Autodesk Docs://David City, NE - AGP/Utilities-2023.rvt”) does not work. Here is what I received from my guy –

" While automating the Revit application UI, I ran into an issue of data inconsistency between what we’re able to pull from the Elastic Search database and what is observable within the Revit application. I am also fully aware that this may be a case of “I don’t know what I don’t know” so please be patient with me. 🙂

When we pull the file path data from the Elastic database, we receive it in the following form:

“file.path” : “Autodesk Docs://David City, NE - AGP/Utilities-2023.rvt”

I thought this path structure was a traditional filesystem directory hierarchy similar to:

“file.path” : “VolumeID://FolderName/FileName.rvt”

However, I now understand the structure to be:

“file.path” : “VolumeID://ProjectName/FileName.rvt”

This small, but distinct difference has caused a problem for me because from within the application, there apparently also exists a traditional folder structure within each project. This folder structure is not accounted for within the file.path value we are able to retrieve from the Elastic database. Maybe that means the folders don’t actually exist and they’re an intricate representation of a tagging system intended to make users lives easier. Or maybe they do exist but for some reason the Bimbeats Elastic database doesn’t require them in order to function… I really can’t determine."

Any Ideas what I could do?

2

Update - It looks like my guys are looking for the Saved file path. It would show the folders in addition to what is in the current file path.

3

@Gilly I had a look at it and this is correct on our end. Autodesk doesn’t return the full file path (saved path) for models. It will only give you the hub/project/file. That full file path with subfolders only kind of exists for BIM360 website users so it appears files are stored in subfolders. We can get that full subfolder structure from ForgeAPI (APS) but for the Bimbeats Revit plugin, we didn’t need that. To open a file saved in BIM 360 you just need that path and then use the ModelPathUtils.ConvertUserVisiblePathToModelPath(). I think that’s why Revit APIs don’t return the subfolders. They are not needed to access the model. You either need the path that we already provide, or ProjectId and ModelId which then allows you to create that same path.

In any case, your coder is correct that these only exist in the BIM360/ACC world and are used to create the tree structure in the website, but from Revit’s point of view, they are not needed to access the file. I agree that it would be nice to get them because then we could do some additional analysis on files and folder structure in ACC, but for that, we need APS APIs, not Revit APIs