Nested links When sharing and consuming models.

[ChrisGamble]

We shared a package containing a building model that has unit linked into it (attached), and the units included in the package.

Our MEP consultant has consumed the package. But when they link in the building model, the unit links break. 

I have gone in the consumed model and the unit links repathed correctly to the consumed folder when they consumed our package.

If everything is pathed correctly, why would links break as if they cant find the file in the consumed folder?

I have read that cloud workshared models do not support nested links  but according to that article only the 2nd and 3rd and so on layers of nested links are not supported. Our models only have one layer of nesting, the unit link. 

Can someone explain in detail how nested links are treated when working with cloud workshared models in BIM 360?

[ChrisGamble]

As a "whatever, just try it" idea, we pathed the link to the consumed folder through the desktop connector, and that allowed the links to load and appear properly. I know from this link that is not the proposed workflow for linking in cloud based workshared models, but it worked fine. 

Could someone explain to me why that is not a suggested option when linking in cloud based workshared models? Is there anything wrong or something with going through the desktop connector that could corrupt files?

[ericJ9ZDG]

Are all the models cloud hosted?

[ChrisGamble]

Yes.

[ChrisGamble]

Still looking for assistance, if anyone is knowledgeable on the topic.

[múinteoir]

What access have you assigned to the MEP team? They will need at least view access to allow the live linking to work.

More info here - https://knowledge.autodesk.com/support/bim-360/getting-started/caas/simplecontent/content/understand...

[ChrisGamble]

We are not live linking, we are using the consume method. They have View+Download+Upload permissions to the shared folder, and V+D+U+Edit permissions to the consumed folder, inherited from their team folder.

[ChrisGamble]

Still looking for an answer on this topic, if someone is knowledgeable on the topic to help me troubleshoot this.

[pedro.hf.silva]

Hi Chris, we had lots of similar problems in here. If you can, try giving your MEP consultant permission for viewing and downloading files directly from the building model team folder. Maybe your central file is looking for the nested links files in their original folder.

[ChrisGamble]

---

@pedro.hf.silva wrote:

Hi Chris, we had lots of similar problems in here. If you can, try giving your MEP consultant permission for viewing and downloading files directly from the building model team folder.

Our company policy is to use the consume method, to insure we aren't oversharing our models and hindering access to our intellectual property within the files. 

Maybe your central file is looking for the nested links files in their original folder.

Maybe, but that's not how BIM 360 operates to my understanding. Once you consume a package (with all nested model included), BIM 360 updates the file paths of those nested links, so when you link in a consumed model with nested links, the links appear, at least the first level of nesting appears.

---

[ChrisGamble]

Still looking for assistance with this, both the first and second comments.

[BIMologist_]

Me too. @ChrisGamble   a bit frustrating. 

[ChrisGamble]

Still looking for assistance with this matter. These issues persist.

[GPnmulder]

By 'containing a building model that has unit linked into it (attached)', do you mean the unit links are linked into the building model which is then linked into the MEP/consultant's model?

I don't have a vested interested in the topic but, in reading the Autodesk answer at the link you provided, their example seems to match your situation and 'is behaving as designed'. Any nested (attached) link beyond the first linked model is not supported and will not appear.

The functionality has been requested on the ideas page here: 
Nested Linked Revit Models do not display when model is published to BIM 360 

[ChrisGamble]

That link is actually referring to the model viewer online. 

But I am no longer pursuing answers for this. We have been having our consultants link through the DCA and that seems to be working, even though that is not the proposed method autodesk has written up for linking consumed models.

Thanks for everyone's responses.

[pgandolfo]

Hi Chris, 

I'm curious if you are still having your consultants link thru the DCA, or if you have found another way for the "attached" unit links to show up in the consultant models when they link to the Architectural shared or consumed model. 

Also, did you ever find out why linking to the DCA is not suggested? I found an old blog post that gave me a clue, but I have not been able to find anything concrete. 

Thanks!

[ChrisGamble]

Linking through the DCA is a fine process to use. No issue linking and displaying the first level of nested links. 

[edmon.moussallyBKA49]

Hello @ChrisGamble , We are facing the same issues, maybe a dumb question but What is the DCA?

[joseph.willems]

Hi @ChrisGamble We are having a similar issue (multi family apartment building with units as nested links) our MEP consultant cannot see them (gets the "The following nested links are not found. These links will be unloaded:). I suspect that the model in our shared folder is trying to access the units in their original location (in our main working folder that he obviously does not have access to) did you ever find a solution? I have always in past projects just published, downloaded and sent them our files so that they can as they please with it.

[joseph.willems]

To anyone still interested We did find a solution. For some reason nested link file paths won't update when placed in the shared folder on BIM 360 like they would in any other situation. The solution we found was to grant the consultant View + Download access to our working folder (where are live model and units reside) that way the file path for the model they linked will be valid. I recognize this may not be acceptable to some firms but it is the only to use the shared folder with nested links.