The "New Version on Server" message is confusing to those used to Track Changes verbiage
Several users familiar with Track Changes functionality in MS Word (all versions) are having trouble with the wording of the "A newer version of the file is available on the server" "Discard Changes" button when opening a file from Teams
At issue is the expected behavior of a Word document and the resolution of warning messages.
Our researchers will verify that the latest version of the file in question is available on Teams via Word Online and then open the file in Word (Open in Word) using the Teams interface.
When the file opens, whether in Word 2016 or Word 365 (1808) it will inevitably open as Read-only (marked as such on the title bar) and a message will display: "A newer version of the file is stored on the server" with two buttons: "Save As" and "Discard Changes"
Because of their aforementioned familiarity with Track Changes, the wording of "Discard Changes" means a very specific and undesirable thing to them and as a result - regardless of the advised resolution procedures we have provided - they will balk and click Save As, creating another version of the file rather than accepting that Discard Changes in this context refers only to the local file.
Now to my ask, is there any way possible to change or in some way update the Discard Changes button to something more descriptive of what will actually happen to the file, perhaps "Reload from server" or "Retrieve latest version" so that we don't have researchers working on actual cures for cancer losing valuable work time trying to decide if their changes are really saved. Thank you!
If the location and timestamp of each object involved is included in the message, that will reduce the ambiguity of the situation. Obviously, if there are two or more edits occurring simultaneously, some kind of intelligent merge might be required.
Google Handles this almost as well as I would like, by having only one shared copy, with each editor's insertion point identified and moving live, but it does not 'mark' the currently changed text for each editor so that editorial collisions are apparent to all participants.