Replace a BIM360 Design Model

[Anonymous]

Is it possible to replace a BIM360 design model that is already initiated in the cloud with another one that has been provide via file transfer.

It’s a customer who is using design to collaborate their own model but the rest of the design team don’t want to engage.

[AdamPeter]

Unfortunately not as a continuing version to the existing file. There are basically 2 options.  First would be to delete the existing file and upload the new one with the same name.  Any links would need to be fixed as technically behind the scenes the system sees it as a new file even though it has the same name.  The second option is to rename the existing file to another name so you can at least retain the history of the file and then do the rest as stated above.  Hope that helps to at least clarify.  I can see where uploading as a continuing version may be nice.  You can always create it as a new idea on the idea station as well.

[s.odwyer]

Hi Adam,

Which option would you recommend? I have a customer using the desktop connector to LIVE link the models to their collaborative model but its not linking the versions correctly. 

Sean

[AdamPeter]

Generally, I would recommend the rename option as you can at least keep history that way.  If the replace is frequent though you may get a lot of files which could be confusing.  I suppose you could move them to another folder to clear things up.

[anil_mistry]

Hi @s.odwyer,

I am checking back to see if one of the great posts in this thread helped you with your question. If so, please take a moment to reward the poster or posters with a Kudos and select the Accept as Solution button on those posts that helped.

Thank you and have a great day!

[s.odwyer · Accepted solution]

Hi all.
I ended up going a different approach.
I uploaded all"linked" design models as dump models. Then linked them via the desktop connector into the bim360 collaboration model. It's alot easier than renaming the linked models and re initiating them as cloud models. These models could be updated every week. Having the option of dragging and dropping the files into docs, version controlling them and then looking them into the design model is the easiest route.

Sean

[anil_mistry]

Hi @s.odwyer,

I am glade its working out for you. Please let us know if you have any other questions or concerns.

Thank you and have a great day!

[travis.temples]

Would doing the rename option still have the same effect on hosted elements and Revit seeing it as a new file?

[NickScalone]

Hey Jonathan

How is the process working out for you?  We are doing something similar: Design architect isn't working in the cloud, so they give us a dump of models every week or two.  We take these models, put them in the "shared" folder where they would have gone (if they were using design collab) and then these models get linked into the other consultants models.  No consuming for these, just controlled linking.

We just started this, so any updates you can provide on your situation would be great!

Thank you

-N

[s.odwyer]

Hi,

Using the desktop connector is the best way to link in non worksharing models. 

If you have them in Docs and link them through the Destktop connector any updates to the models will be linked to the design model.

Only downside to this is that viewing these DC linked models as references in docs will not be achievable. as in if the architects model was linked it will not be visible in docs but will be in revit. 

Sean

[Anonymous]

What I find difficult then is turning on grids...

When I have my linked file  as collaborative I can easily turn off the shared levels and grids so that I won't have to go in any view template and turn these off. 

I follow the collaborative process and erasing the model in the cloud each time. If there are any other suggestions to handle linked files's grids let me know

[joe.trestick]

Can you please expand on "dump models"?  I am having issues with this step and am probably missing something.  If I just drag and drop a Revit model into the browser folder and try to link it via "insert Revit link" it is not available/visible.  When I save as either a work shared or a non-work shared cloud model I am not able to overwrite it.  I still get the error no matter what when trying to overwrite/update the model via "drag and drop" in the BIM360 browser.  Any help would be much appreciated.  It takes far to long to re-initiate the cloud model and then "reload from" in Manage links.  I like the idea of what you are doing and would really like to replicate this workflow for ease of updating the links from external sources.

[s.odwyer]

Hi. 
in order to have the linked files visible in the Revit link is to initiate the linked model as a revit cloud work sharing model. To do this have the model open in revit and go collaborate and initiate it from

there. Saving a central model or local model to Docs won’t work. Note you cannot delete an initiated model. 

you can of course link in a non initiated model via the desktop connector but I would advise on the initiated model as it’s faster. 
Hope this helps. 

sean

[s.odwyer]

Hi. 
in order to have the linked files visible in the Revit link is to initiate the linked model as a revit cloud work sharing model. To do this have the model open in revit and go collaborate and initiate it from

there. Saving a central model or local model to Docs won’t work. Note you cannot delete an initiated model. 

you can of course link in a non initiated model via the desktop connector but I would advise on the initiated model as it’s faster. 

regarding your image that means you are trying to overwrite an initiated model

currently in docs with a local. Try initiating into a different folder. 

Hope this helps. 

sean

[DeepakMaini]

@joe.trestick in addition to what @s.odwyer mentioned, you might also want to look at the Saving Cloud Model workflow I showed in this thread. Please note that in your case, step 1 will only be for the non-cloud workshared models.

https://forums.autodesk.com/t5/bim-360-support/level-of-bim-360-required/m-p/10000079/highlight/true... 

[ruben.romeroVFC4C]

please fix this ASAP

[Anonymous]

Hi Adam,

Have there been any developments with implementing the ability to supersede existing BIM360 files?

As you discussed in your post, there's currently no procedure for superseding manually uploaded BIM360 Revit files, however after discussions internally and with other consultancies, I feel that it's a common enough occurrence to warrant the ability.

Many companies are hosting their own internal projects and manually uploading linked models when a collaboration project hasn't been initiated by external parties (a similar workflow to the old Revit servers).

With the upcoming discontinuation of the Revit servers I feel that having this functionality would be critical. Allow continuity of these uploaded files is a big factor, as well as simply house-keeping - having one file rather than a number of old, renamed files.

[Ar.SalmanHasan]

Hi All,
I have tried one method which has worked for me. I wanted to retain revision history while replacing BIM360 model.
Try if it works.

Step 1 - Locate the local file of the BIM360 model in CollaborationCache (Local drive).

Step 2 - Rename your latest model as per latest local file.
In my case the name was something like ''335bf908-4eea-4414-8598-a820fa028597''. Try to recognize the file by size or date.
Step 3  - Replace the local file with the file you have renamed.
Step 4 -Open the replaced file,  synchronize and publish accordingly.

Your BIM360 model will be updated as per latest updates.

[opesch_]

Hi, I was very interested by your method Hasan but it didn't worked for me.... (BIM360 & Revit 2021)

How do you address the fact that the "inbound" central model path of the received model is different than the one of the cached local model you are overwriting in collaboration cache?

When I overwrite the cached model with the renamed one, I just got the warning that the file was moved from its original path and cannot find its central file !

I tried with the local file I received and I tried by detaching it too....

😞