ok, I "think" I see what's happening now. This is usually caused because the model was deleted from the BIM 360 Team site instead of from the "Manage Cloud Models" dialog inside of Revit. It's key to know that what you see in Revit is actually on the C4R service as the central model and what you see on the BIM 360 Team page is a detached copy of the live central that is published (which is why you would also see version differences between the two as well). So, when you delete the model from BIM 360 Team you are deleting the copy, not the actual model.
Now, the issue becomes then, that you are trying to delete a model in C4R that no longer has an associated file on BIM 360 Team and so that prevents the delete (or rename). You can correct this by doing the following
- Open the existing model from C4R in Revit
- Perform a SWC with no changes to the model
- Close the model
- Republish the model from the "Manage Cloud Models" dialog
- Attempt to delete the model again
In this way you basically force C4R to see an associated model in BIM360 allowing it to be deleted from the C4R service. Definitely something we are looking at from an expected behavior standpoint moving forward.
If this does not work for you, please let me know and I can look into it further. Also, thanks for the suggestions on the rename requirements. Feedback is always appreciated!
thanks,
Adam Peter
Customer Program Manager
Autodesk