SharePoint
Feedback by UserVoice

I suggest you ....

← Sites and Collaboration

Requests for correction on behavior to open in edit mode of SharePoint Online and OneDrive for Business due to specification changes on MC 1

When opening Word, Excel, PowerShell files of SharePoint Online and OneDrive for Business in Office Online with MC 131670 published in Message Center, it opened directly in edit mode.
As usual, please restore it so that it can be opened in viewing mode by default.
Or, add setting items so that you can select edit mode or viewing mode as the default value.

481 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

YH shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

63 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Beth Beck commented  ·   ·  Flag as inappropriate

    Please change the default behavior to allow Edit or View on a library by library basis. A major issue I've run into is when using Power Automate (Flow) action "Update file properties", I constantly received The file "https://<mycompanysite>/sites/<libraryname>/FileNameTEST.docx" is locked for shared use by... So anyone could have the file open and I need to update properties of that file such as Status choices or Approval Notes. In this case, the Flow will fail unless you have a workaround, such as another step after it - configure run after set to "Is Successful" or "Has failed".

  • Michael P. commented  ·   ·  Flag as inappropriate

    As previous comments have said, at least provide admins an option to change what the default behavior is, instead of changing it on us with no option to revert. Unacceptable.

  • Mike Richards commented  ·   ·  Flag as inappropriate

    Please fix this absurd behaviour asap, the constant accidental altering of files or even just modified dates with the combination of default edit and auto save seems like a pretty poor trade off against simply having to click edit before changing a document.

  • Paolo Tomasi commented  ·   ·  Flag as inappropriate

    The current behaviour is plainly stupid, Microsoft. Are you jusy trying to increase the number of versions, so you can charge more for storage space?!? The default behaviour by site MUST become customizable, particularly as opening in view mode WAS the default until quite recently!!! And it worked perfectly.

  • Janet Henry commented  ·   ·  Flag as inappropriate

    When is this going to be addressed? This has been on their radar for two years now and no response from the team? They need to make it an administrator setting for the sites, this is a disastrous set up.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please allow the SharePoint Administrator to "choose" an option to have Word documents open in full view or edit view. When you use the "Share" feature to send a word document and an end user opens it they see the edit view and have to click on view and then again click on reading view to see it displayed with the header and footer. It is not professional looking to send a document in "edit view" and force my end users to complete two more steps. This should be an easy fix. Headers and footers for Procedures hold valuable information that needs to be seen.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This odd feature of opening in edit makes it really hard to keep track of versions, and is confusing to users who are just trying to look at a document (probably this is the case vast majority of the time). Should open in read only and the user given the option to change to edit mode.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Without a doubt, these files should open as read only by default. Users most often just want to view the contents of the files without editing. When the file opens in edit mode, by default, it saves the item as a new version, records your name as the modifier, even if no changes were made. Not efficient from a compliance perspective.

  • Dave commented  ·   ·  Flag as inappropriate

    Unbelievable.
    I just spent a week with MS Support due to our auditing showing a significant increase in edits due to all documents being opened in edit mode online. Most edits were accidental / unintentional. To add to the user confusion, documents now open with no header or footer. Supports official response:
    -----
    We can achieve it using the "Protect Document" option.
    1. Open SharePoint document
    2. Click on File > Info
    3. Select "Protect Document".
    Currently, we do not have any option/setting to apply protected view for specific site or to whole tenant.
    ----
    We are now looking at the very painful proposition of migrating back to on-prem servers which do not have this particular “feature”.
    Not sure how or why MS thought this was a good feature. Needs to be remediated ASAP.

  • Anonymous commented  ·   ·  Flag as inappropriate

    I can't understand why this does not have more voting...

    Opening documents in edit mode by default combined with the autosave feature is jeopardizing the draft/approval features.

    People are opening document for viewing and regularly we find documents generating a new draft/version when there was no intent to modify the document and it starts an approval process.

    This make no sense at all. I can't understand how business are using these features efficiently...

  • Cory Kennedy commented  ·   ·  Flag as inappropriate

    This is so important. As a customer recently going live with this product to host some internal documents it is very difficult to keep reminding people that it will be autosaving all changes. Plus the fact we can't stop people sharing and granting others access through a link, the non super users then also have access and start editing templates and policies! This needs to be addressed

← Previous 1 3 4

Sites and Collaboration: Document Libraries

Categories

Feedback and Knowledge Base

(thinking…)


SharePoint Tech Community

UserVoice Terms of Service & Privacy Policy