Tool

Save as central

Technical name: salva_come_centrale

Project › Team

Team

Saves the workshared model as a new central model at the path you give, like Revit's "Make this a Central Model after save", after your approval in Revit.

What it does

Saves the workshared document as a central model in an .rvt file, like Revit's Save As with the option "Make this a Central Model after save": from then on the team works on that file, and each person creates their own local copy.

The path is the full path of the new .rvt file, on this PC or on the network (C:\… or \\server\…), in a folder that already exists. If the file is already there, BIMit replaces it only if you ask for it explicitly: if it is a team's central, replacing it affects every colleague.

A new central in the system temp folder (%TEMP%) is a test model: no colleague uses it, and BIMit saves it without asking for your approval.

How it works

  1. You ask your AI to save the model as central and give it the path; it prepares the request and gets the job number right away, without being blocked.
  2. BIMit checks the path and the document and brings Revit to the front with a dialog saying what is asked: document, new central model, whether the existing file will be replaced, and what will happen.
  3. To approve, tick "I have read the request: I approve this action only" and choose "Approve: save as central"; "Deny" does nothing. Revit saves right away.
  4. Meanwhile your AI follows the request with Job status and at the end gets the path of the central. Until you answer, it can withdraw the request with Cancel the job.

Example requests

  • "Save this model as central in S:\Projects\C24-017\C24-017_central.rvt."
  • "Create the central in C:\Projects\Smith House\SH_central.rvt."
  • "Replace the existing central in C:\Projects\25001\25001_central.rvt with this model."

What changes and how to undo

After your approval, Revit writes the new .rvt file as the central model and the open document becomes the central itself: to work on it as a team, everyone (you included) creates a local copy. If the file existed and you asked to replace it, the previous file is replaced: if it was a team's central, what colleagues have not synchronized can no longer get there. If you deny the request, or your AI withdraws it before you answer, nothing changes.

Saving as central cannot be undone with Ctrl+Z: that is why team actions ask for confirmation in Revit, except a new test central in the system temp folder (%TEMP%).

Limits

Your AI's access level must be Team: only you raise it in Revit (Level), for a time you choose, and it goes back to the default level when that time ends and at every Revit start.

  • The document must already be workshared: worksharing is turned on in Revit (Collaborate › Worksets), then you save as central. A family does not become a central model.
  • The path must be complete, end in .rvt and be in a folder that exists; cloud centrals are not created from here.
  • If the file already exists and you do not ask to replace it, BIMit stops and says so.
  • It does not start while another operation is in progress in Revit.
  • The dialog only accepts an answer given by a person: with the box ticked and after reading it; while Revit is playing a journal the request is denied.
  • While the dialog is open, the other tools that use Revit answer that Revit is busy.
  • Only one save-as-central request at a time can wait for your answer.
  • A worker Revit (opened by BIMit in the background) does not do team actions, except a new test central in the system temp folder.

Parameters

ParameterMeaning
percorsoFull path of the new .rvt file. Required.
sovrascrivitrue = replaces a file that is already there (default false).
attesa_sSeconds to wait in this call for the job to finish (0-120, default 0).

Related tools

All tools