The below Knowledge Network page goes into depth discussing best practice on Upgrading a Workshared Project.
I am assuming this is more specific for upgrading to a new product year, but does this/should this also go for Revit Updates from a previous build such as 2019.2 from 2019.1 or even ?
I highly doubt that we've done this in the past. I am wondering what sorts of issues might be faced if this isn't followed? (FYI: We do file-based central files.)
Autodesk Knowledge Network - About Upgrading Workshared Projects
Builds and Point releases do not involve a file format change so no file upgrade is involved. The new release each year involves a file format change and that's where the upgrade is involved.
Updates (point release) introduce new features mid year (tools that are code ready with no file format required) and may contain code repair (fix bugs) where builds just deal with fixing code/issues. Our installed release has a bug. The new build fixes the bug. If we install the new build for some PC's then those PC's fix the bug and the other pc's introduce the bug again, like passing a cold around the office (also important - same operating system version).
All the PC's that edit a given Revit file should be using the same build/update. Nobody should believe it is okay to just apply a new build/update to their PC without involving the entire project team in the conversation.
Upgrades require planning and everyone involved with the project (editing Revit files) must do so together (at the same time). If that can't be done, don't upgrade the project. Whoever does will either force the other team(s) to upgrade when they aren't ready or they team that does upgrade will have to abandon any work they did in that release and return to the older file.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@SteveKStafford wrote:
Upgrades require planning and everyone involved with the project (editing Revit files) must do so together (at the same time). If that can't be done, don't upgrade the project. Whoever does will either force the other team(s) to upgrade when they aren't ready or they team that does upgrade will have to abandon any work they did in that release and return to the older file.
Big Ditto!
Can't find what you're looking for? Ask the community or share your knowledge.