Overwriting changes with multiple users

The smartsheetesque approach to this would save sheet edits when you click the refresh link on the popup notice about collaborative changes that have occurred on the sheet. The alternative is someone else losing their stuff, but at least it's in the Change Log. As it stands, we would lose the history of our intended changes, and that seems like a considerable problem. The closer Smartsheet can get to the way G-docs works, in terms of collaboration and versioning changes, the better. And, on that point, real-time collaboration would be preferred over post-save atomic level undo/redo (if a choice has to be made).

I also agree with Roger.  "The closer Smartsheet can get to the way G-docs works, in terms of collaboration and versioning changes, the better."

A meeting is not always necessary or even beneficial for collaborative work.  For example, we would like to transition our corrective action log from Excel into Smartsheet.  At any point in time there can be up to 5 individuals processing corrective action requests from each of our global plants.  If all of them are attempting to assign the next available CAR# on line 107, 4 of them will lose their information.  

Unfortunately, while demonstrating the benefits of converting from Excel to Smartsheet to the group, our Plant Manager logged in and made changes to the same field I was working in.  I ended up losing the information I was presenting.  It is not truly a collaborative function if we are not able to work simultaneously in the same sheet and receive real time updates. This will likely be a make or break for our company's expanded use of Smartsheet. Very disappointing.

I would like to add my voice to this request - we have recently introduced Smartsheet to the business and it will fulfil the role of a project management tool. However, our clever IT team spotted an opportunity to use this instead of a Google sheet and rolled out an onboarding solution - it is only now that we have identified that as different team members add new rows at the same time, data gets into a mess. 

We can try and educate them to save every time they make a change or start a new row, make sure they refresh when notified and save before they refresh but for a team that is used to Google Docs and Google Sheets, it's making Smartsheet look like a bad decision. . .