Navisworks Coordination Add-in : Non-coordination models breaks workflow

[Chad-Smith]

Using the Navisworks Coordination Add-in on a project that has appended models not in the BIM 360 coordination space breaks the entire workflow.

E.g. At the time of writing this, all my project models come from a BIM 360 coordination space except for a ReCap RCS model, which while it's stored on BIM 360 it is instead appended via the Desktop Connector. This is sufficient to break the coordination workflow.

I would like to see improvements made so that non-coordination space models do not break the workflow. There has to be a way to gracefully work around this scenario.

[Ezekiel12]

Linking files to Navisworks via Desktop Connector is really broken in many ways. It simply do not work and I had a lot of discussion with Autodesk last few days and they basically do not recommend it at all. 

It baffles me. Navisworks is great and the need for linking cloud models is huge. But the implementation of cloud and Navisworks is simply bad.