|
active
Joined: Mon, Mar 14, 2011
21 Posts
No Rating |
This has happened to me on several occassions...I will have completed tasks in the model only to come back several days later and find that they have reverted back to an earlier version of the model where that work has disappeared. The program (2013) doesn't crash and the other few people in the office seem to be using worksets in the (semi-)appropriate way. And it's not like the whole model has gone back to an earlier version...just select parts.
Since we have relatively few people working on a project at once, we do not bother breaking elements out onto specific worksets, but rather folks borrow elements until they are relinquished during a synch.
Trying to diagnose the problem and believing that it could have been an issue with people in the office using (and synching) an older version of the model, such as if they continue to open up their local copy every day rather than creating a new local from the central at the start of the day, I sent the message describing the best practices way of opening/synching and it was clearly understood by my colleagues.
This has happened in everything from schedules to walls to annotation, so it seems to cross the gamut. Has anyone else experienced this issue and is there a possible fix? I'm almost to the point of believing in conspiracy theories and that my system is being hacked by Revit Goblins when I'm not looking! Help.
|
|
site moderator|||
Joined: Fri, Nov 12, 2010
1749 Posts
 |
Revit doesn't just go back or delete things on its own. If you have a central file someone may not be using a local file or using an old local file that is screwing up your project. This is most likely a process problem in your office.
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
 |
This is a process problem in your office. You need to retrain the staff on how to use worksets. Someone is working in the central or over-writing it. Syncing an older local with the central will only add CHANGES that user made. If someone is checking out worksets and working at risk, be careful!
|
Search