Revit linked file not showing in BIm360 docs viewer - external resource button

[Renzo_van_Rijswijk]

Hello, my collegue has an issue with Revit 2022 and BIM360 Design Collaboration. For some reason after initiating the project in BIM360 the external resource button is not working properly. It doesnot do anything. The result is that when he links a Revit model from the consumed folder and updates the model (reload latest). The linked model is not shown in BIM360, whereas others do not have any probem with it.

Do you have a fix for this? Gr. Renzo

[gareth.spencer1]

Hi @Renzo_van_Rijswijk ,

Just to confirm when you consume the model it shows in the consume folder right?

If can see the model and have managed to reference the model into your model. Then when you publish the model have you published the model view with the referenced file switched on?

[Renzo_van_Rijswijk]

 

Yes, when we allways do that in that way. 

So, if I do this. It all works fine. I am directly referred in the Linked model dialog to my project on BIM360.

When my colleque is doing this. And uses exactly the same steps, he does not get referred in the linked model to our project. The "external resource" button does not do anything. So, he searches the to be linked model via the Windows Explorer... like Autodesk Docs\[hub]\[project]\01 wip\Consumed\[team A]\model-to-be-linked.rvt

So, yes in Revit the model is shown in the 3D view. So, it is switched on. We do see it. This 3D view is in the publish settings selected. Then, after a Publish latest (in the cloud or within Revit) the new model is shown in BIM360 docs. However, without the linked model...

Already, we reinstalled Autodesk Desktop Connector. (newest release) but that did not help...

Gr. Renzo

[gareth.spencer1]

So, are you saying that he cannot see the project folders through Revit, is that even if you dropdown the list and select on this computer. Then selecting the hub > Project > folder location?

I know not having the correct build of Revit can cause issues. So, lets say as an example you are using Revit build version 2023.0.2 (23.0.20.21) but they are still using 2023.0.1 (23.0.11.19). You might want to check this.

Taka a look at the following article from the Autodesk Knowledge Network, it might be able to help. A consumed workshared model does not show up under the 'External Resources' section in Revit.?

[Renzo_van_Rijswijk]

Hi,

The main problem is that the linked models are not shown in the BIM360 viewer. Allthough we do exactly the same. Almost, because I am in the BIM360 project instantly when I want to insert other models, whereas my collegue is not.

So what is happening here?

Yes, he can go from Autodesk Docs\[hub]\[project]\01 WIP\Consumed\Team A\To-be-linked-model.rvt. But that does not solve the issue, because the linked model is not shown in the BIM360 viewer.

I suspect that for some reason his Revit version is not setting the BIM360-project properly. Besides, the "external resource" does not do anything either. 

I will ask him what build he is using.

thanks in advance, Renzo

[nolangene]

Clarity is needed here. The BIM viewer will only show what is active in the default 3D view (if no published set is setup/selected). Make sure he is publishing a known view. I.E. BIM360 3D etc.... Then make sure that 3D view is setup to show what you need to see. Then sync. and publish the model. The BIM360 viewer should show what you see in the BIM360 3D view setup to publish.

[nolangene]

Edit to my post above. The BIM360 viewer is controllled but what is setup in the Publish model settings. Has nothing to do with the consumed, shared, etc... on the workshared side.

[Renzo_van_Rijswijk]

Hi,

We setup our Revit 3D views in such a way that users see our model with linked models in it.

Of course, we select these in the Publish Settings and make the set active...

Save to central. Publish latest...view the model (with linked models) in BIM360 Docs. 

In this case for some reason the linked models are not shown, whereas the 3D view in Revit does have these linked models. At the moment it only happens on one computer...

Gr. Renzo 

[Renzo_van_Rijswijk · Accepted solution]

Okay, we had to remove the whole Microsoft Profile and create a new one on the laptop. Now it is working fine...