File collision: When two people on two different computers edit the same file at the same time and the system requires your input on how to handle the different versions.
Creating a File Collision (example)
Both UserA and UserB open the file TEST.DOCX from the Team Share TESTING. At this point they both have identical files. However, UserA make some changes and saved file TEST.DOCX on their computer. This is automatically synchronized to the cloud server. UserB still has the same file open and the system cannot synchronize the updated file to their computer. UserB now makes some changes and saves the file. The system sees that the TEST.DOCX file was modified on the cloud server and the collision happens. The system cannot incorporate UserB’s changes into the file on the server. Now there are two copies of the file that are different. UserB will get notified that the collision has occurred.
Three Indications a File Collision Exists
A message that displays briefly in the bottom right corner of the screen.
In UserB’s folder where the file is, a yellow exclamation mark appears over the icon.
The Omega Drive icon will no longer have the green checkmark but will show the yellow exclamation mark.
Resolving the File Collision
There are two ways to resolve the file collision. One is from the System Tray icon and the other is from the file itself.
From the System Tray:
Click on the System Tray Icon and a window will appear.
Click on the yellow exclamation mark.
Another window will appear that will show all the files that have a collision.
Click on the Resolve link and a small menu appears with two options.
Discard: This will delete the file that you saved and your changes will be discarded. Use this option if you are certain that the changes you made are not needed.
Rename: This will rename your version of the file to “TEST (your name collision 0).docx”. Now file synchronization will be able to continue and both the server version and the collision file will be replicated to everyone in the Team Share.
From the File Itself
If you see the yellow exclamation mark on the file you can resolve the conflict directly from the file.
Right-click on the file and from the menu that pops up, navigate to the Omega Drive portion and another sub-menu will pop out.
There you will have the same two options, Delete Local (delete your changes) or Auto Rename Local (create the collision file from your changes). From here you can follow the steps above to resolve your file conflict manually.
Locking Files to Prevent Collisions
If the files in your Team Shares are Word, Excel and PowerPoint files then Omega Drive can be set to allow a user to lock a file when they are editing it. This will prevent others from being able to save the file while it is being worked on, thus preventing File Collisions. Ask the Omega support desk to turn on this feature if desired.
When this option is turned on you will be presented with a window asking you how long you want to lock the file for.
Click the Max Duration drop down to change the time two 2, 4, or 8 hours. You can also “Change Future Behaviour” so that you are not prompted about the locking the next time.
When you lock the file and someone else tries to open it they will be allowed to open it in Read-Only mode. The title bar of the Word document will indicate it is Read Only.
If you go to save that file you will get an error on the save and you will need to change the file name.
When an Excel file is locked by someone else you will again be able to only open it in Read-Only mode but you will get an extra window telling you of the lock.
PowerPoint, like Excel, will give you the extra warning window when you open a file that is locked by someone else.