Forum Discussion
Microsoft Teams not closing document
Hi! I'm having a problem with closing an excel file. I'm in a group with my classmates, and the teacher has added a tab called excel. This is next to the tab called 'files' When I open this tab, it ...
Hi Aileen, we have the same issue here. Users complain about not being able to close Excel documents clicked in Teams tabs. Since you posted last year, maybe you found a solution?
Kind regards,
Kind regards,
- This is just something users have to get used too. The cloud is always online, always open. Files edit in real time, save in real time etc. There is no more "Close" per say. Tabs in Teams are just online web views of files with office online so it's going to edit live. This allows for co-authoring and multiple people using the document at the same time etc.
The only way to edit documents offline is to use sync, and turn off the option in the sync client to Use Office to sync files. Otherwise opening files with auto save off will lock the file and prevent others from opening etc. But you also run the risk of sync issues if you open offline and then save after making changes as others can make changes at the same time.
Anyway, bottom line is users have to get used to the new way of working on cloud documents and just moving away from documents and not having to "Save" or "Close" them. It's an adjustment but they will get used to it.- Thank you Chris for your reply.
I thought that whether a document is hosted in the cloud or on a "regular" server does not make things different: I still "open" and "close" the document, and the server allocates more physical resources when the document is "opened" than when it is not. If what you say is true, would that mean that cloud servers require much more computing resources to hosts 1'000 documents than regular servers? (you seem to say they are always "open")
Same goes with the "save" function. I cannot find a technical requirement or constraint that makes this specifically a "cloud" feature. I have seen many applications implement continuous saving without the cloud, for decades. A good example of this is Onenote. Wouldn't this contradict what you proposed?
On the other side, I also think it is not a good practice to tell users to just accept things as they are and get used to it when they notice something wrong. If a user interface shows a button labelled "close" when a document is opened, and clicking on this button does nothing, I think it is a failure from the editor, and that should be fixed.
Of course, the editor could simply remove the button, as you implied, but that would likely make users' experience even worse. Or it could make the button actually work as intended, thus letting users close a document and return to whatever they were doing before opening it.
In summary, I am not sure I can agree with your proposition 🙂
