& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:03
When you are ready to save or share network changes that you have made locally, you can commit them.
00:09
With the commit, your changes are uploaded to the database and merged with other users' changes as a new version.
00:16
An uncommitted network has a red circle at the bottom of the network icon
00:20
and needs to be committed before any changes can be used in a model simulation.
00:25
To commit changes, right-click the network in the Explorer window and select Commit changes to database.
00:31
In the Commit change to server dialog, you can see a summary of the changes that you are committing.
00:37
Add a meaningful comment about the changes, and then click OK.
00:42
Note that you can also use the Save tool in the File toolbar or the Network, Version control menu to commit changes.
00:50
Every time a change to the network is committed, a new version of the network is created.
00:55
The Commit history details each version of the network.
00:60
From a Commit history, you can view, compare, and roll back changes.
01:05
Even if you are working alone, you can benefit from the commit history.
01:10
To view the commit history, right-click the network in the Explorer window and select Show Commit History.
01:17
For every commit, there is a corresponding version number, date, user, and the number of changes that were made.
01:25
Select an available version and click Details to see the commit details.
01:31
If you want to compare the differences between two versions, you can multi-select two versions and click Diff.
01:38
If you want to go back to a previous version, you can use Branch or Copy.
01:43
Branching a subnetwork from your existing model maintains the history between both networks.
01:49
Copying starts a new network, which resets the history to version 1.
01:54
With multiple users working on the same network at the same time,
01:58
there may be a situation where the same asset is modified by two users.
02:03
If this happens, a conflict will occur.
02:06
The conflict is discovered when a commit is initiated or when one of the users selects Update (get changes made by others).
02:13
If conflicts are found, right-click the network and select Resolve conflicts.
02:19
Best practice is to check with the other users involved before confirming a resolution.
02:24
You can also view the commit history of individual objects.
02:29
In the GeoPlan toolbar, click Find in GeoPlan to locate a specific node.
02:35
Double-click the node to open the Object Properties window, and then click Commit history.
02:42
In the Commit history dialog, select a version and then click Details.
02:47
The Object commit details dialog displays all the information for the different versions of the object.
02:54
Select Full history to display a color-coded table of when each item was last edited.
02:59
Recent changes are highlighted in dark red.
03:02
Similar to the network history, you can also view differences between two object versions by selecting the versions,
03:09
and then clicking Diff to open the Object version comparison dialog.
Video transcript
00:03
When you are ready to save or share network changes that you have made locally, you can commit them.
00:09
With the commit, your changes are uploaded to the database and merged with other users' changes as a new version.
00:16
An uncommitted network has a red circle at the bottom of the network icon
00:20
and needs to be committed before any changes can be used in a model simulation.
00:25
To commit changes, right-click the network in the Explorer window and select Commit changes to database.
00:31
In the Commit change to server dialog, you can see a summary of the changes that you are committing.
00:37
Add a meaningful comment about the changes, and then click OK.
00:42
Note that you can also use the Save tool in the File toolbar or the Network, Version control menu to commit changes.
00:50
Every time a change to the network is committed, a new version of the network is created.
00:55
The Commit history details each version of the network.
00:60
From a Commit history, you can view, compare, and roll back changes.
01:05
Even if you are working alone, you can benefit from the commit history.
01:10
To view the commit history, right-click the network in the Explorer window and select Show Commit History.
01:17
For every commit, there is a corresponding version number, date, user, and the number of changes that were made.
01:25
Select an available version and click Details to see the commit details.
01:31
If you want to compare the differences between two versions, you can multi-select two versions and click Diff.
01:38
If you want to go back to a previous version, you can use Branch or Copy.
01:43
Branching a subnetwork from your existing model maintains the history between both networks.
01:49
Copying starts a new network, which resets the history to version 1.
01:54
With multiple users working on the same network at the same time,
01:58
there may be a situation where the same asset is modified by two users.
02:03
If this happens, a conflict will occur.
02:06
The conflict is discovered when a commit is initiated or when one of the users selects Update (get changes made by others).
02:13
If conflicts are found, right-click the network and select Resolve conflicts.
02:19
Best practice is to check with the other users involved before confirming a resolution.
02:24
You can also view the commit history of individual objects.
02:29
In the GeoPlan toolbar, click Find in GeoPlan to locate a specific node.
02:35
Double-click the node to open the Object Properties window, and then click Commit history.
02:42
In the Commit history dialog, select a version and then click Details.
02:47
The Object commit details dialog displays all the information for the different versions of the object.
02:54
Select Full history to display a color-coded table of when each item was last edited.
02:59
Recent changes are highlighted in dark red.
03:02
Similar to the network history, you can also view differences between two object versions by selecting the versions,
03:09
and then clicking Diff to open the Object version comparison dialog.
When you are ready to save or share network changes that you have made locally, you can commit them. With the commit, your changes are uploaded to the database and merged with other users' changes as a new version.
Note: An uncommitted network has a red circle at the bottom of the network icon and needs to be committed before any changes can be used in a model simulation.
To commit changes:
Note: The File toolbar > Save tool or the Network, Version control menu can also be used to commit changes.
Every time a change to the network is committed, a new version of the network is created. The Commit history details each version of the network. From a Commit history, you can view, compare, and roll back changes. Even if you are working alone, you can benefit from the commit history.
To view the commit history:
In the Commit history dialog box, for every commit, there is a corresponding version number, date, user, and the number of changes that were made.
Note: To compare the differences between two versions, multi-select two versions and then click Diff.
Note: To revert to a previous version, use Branch or Copy. Branching a subnetwork from an existing model maintains the history between both networks. Copying starts a new network, which resets the history to version 1.
In a multi-user environment, there may be a situation where the same asset is modified by two users. If this happens, a conflict will occur.
The conflict is discovered when a commit is initiated or when one of the users selects Update (get changes made by others).
If conflicts are found:
IMPORTANT: Check with the other users involved before confirming a resolution.
To view the commit history of individual objects:
Note: Recent changes are highlighted in dark red.
Note: Similar to the network history, to view the differences between two object versions, multi-select the versions in the Commit history dialog box, and then click Diff to open the Object version comparison dialog box.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.