Committing changes to the project file
|
Command |
Path |
|
Save and Commit |
File |
While editing a shared project, update the project file when you’re ready to let other users have access to your changes. How often you commit depends on the size of the project, the number of users, and the network speed.
To commit changes from a working file to the project file:
Select the command.
The Commit dialog box opens.
Click here to show/hide parametersClick here to show/hide parameters
|
Parameter |
Description |
|
Comment |
The Comment you entered when you checked out these layers or objects displays; edit it if needed |
|
Automatically release checked out layers and objects |
Releases the checked out items following the commit |
|
More |
If you have Project permission or above, click More, and then specify whether to commit changes you made to document preferences and view settings. For details about what can be committed for each permission level, see Permission levels for document preferences and settings, and Permission levels for view-related settings. |
|
Opens the Commit List dialog box to show all checked out or modified objects that will be affected by the commit. When you commit, all modified objects will be synced to the project file, and checked out objects will be released. Double-click an item to temporarily jump to it and highlight it in the drawing. Click Close when you're done. |
Click OK.
If there is a conflict between an entity (resource, class, or layer attribute) in the working file and an entity in the project file, you’re prompted to resolve the issue before the commit can continue.
If the working file has an entity with the same name as an entity in the project file (for example, if there are hatch and tile resources both called “brick”), either rename your entity or discard it.
If an entity in the project file has been updated since the working file was created, select whether to replace the other entity, rename your entity, or discard your entity.
If the working file has a story with the same elevation as a story in the project file, either replace the other story or discard your story. (Vectorworks Architect or Landmark required)
If the metadata in the project file is large enough to affect the performance of project sharing, an alert displays. When this happens, the project administrator must ensure that all working files are updated, and then clear the metadata as described in Clearing metadata from the project file.
The project file is updated with your layer and object changes and any other settings you specified. The working file is refreshed from the project file as well.
