Feedback by UserVoice

How can we improve Word for Windows (Desktop Application)? Vote for an existing idea or share a new one.

Missing "Document panel" in Word 2016

In Word 2016 I'm missing the "Document panel" This was something that was made available when enabling "Developer" i Word 2013
We use this a lot when opening Word letters from Sharepoint to enter data into field.

690 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

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

305 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    Please re-introduce this feature. It's one of the key integrations with Office 365/SharePoint. Looking at the Azure Information Protection Labels, this is somehow acknowledged by Microsoft. The old Document Information Panel was however a rusty old feature, that still caused a lot of people misery while still being a key part of a good integration. Please reintroduce this feature on the right side of the screen, maybe in the same way the 'Activity' tab functions. The number of fields will not matter if you use the verticality of the Office clients. and it's hidden from sight whenever you want it to.

    Just like the recently introduced PowerApps Forms Integration for SharePoint, this is vital for Microsoft to invest in.

  • Simon Hudson commented  ·   ·  Flag as inappropriate

    We are actively advising all our clients to avoid upgrading to Office 2016 until this is resolved. Office 2016 is fine, but this absolutely ruins many of their business processes. The backstage view of properties is a complete mess, the web form is slow to open and it's impossible to see the information in the document in order to add the details to the metadata properties.

    It now takes many clicks to even see the properties, interacting with them is a horrible user experience.

    So that's about 250,000 users who are not able to upgrade to Office 2016, and that number is increasing. It is also stopping a large proportion of our clients from taking the Office 365 E3 or E5 licence. They are option for E1 or K1 instead and staying with their current version of Office (2013 or even 2010)

  • Adam Crain commented  ·   ·  Flag as inappropriate

    Bring this back ASAP - we just realized this was lost in the recent version of Office. As everyone else has stated its critical to integration of SP and Office!

  • jon commented  ·   ·  Flag as inappropriate

    Are Microsoft trying to kill SharePoint? The Document Panel is a vital easy to use feature for end users, they see it, they tag it, so simple, just don't get your thinking here. I've really had a battle to sell SharePoint to the decision makers in the business and this along with the deprecation of InfoPath with no clear replacement or roadmap to a replacement, and the deprecation of Access Services when businesses have spent a lot of money on enterprise licences for those features is really pushing business decision makers away from SharePoint altogether, they don't see long term viability in a product where key features that we've spent a lot of resource implementing just get deprecated. And as for a move to the cloud, that looks even worse, you deprecate a feature and get even less time to find a replacement, you have given people using Access Services little over a year until you pull that service. I really embraced SharePoint, but moves like this are damaging the trust of business leaders, and technology implementers everywhere.

  • Anonymous commented  ·   ·  Flag as inappropriate

    The document panel is a vital tool for working within a document management site using a content hub. We have almost a thousand content types for record management, and the removal of the document panel doesn’t provide any options for content management when you have the document open on your screen. Going to the information area, turning on all properties, half of the fields listed are unusable – I want to see my content metadata fields, not the Microsoft generic ones.

  • Thaddeus Ferber commented  ·   ·  Flag as inappropriate

    Any updates since last August?

    To drive user adoption I need the managed metadata tags to appear at the top of microsoft word documents. We tried to get
    staff to click on the file tab but that ended up being too many clicks so everything stopped saving things in SharePoint.

  • danielb commented  ·   ·  Flag as inappropriate

    surely we have not let people depend on something and then take it away from them in one swoosh. Removing the document information panel will take us backwards. I implore MS to please make this feature available. Without it I might as well be using a pencil and notepad.

  • rwalka commented  ·   ·  Flag as inappropriate

    this is insane. Taking away Visual from SP Designer 2013 was bad enough. The fact that there's still no answer, I would really like to see some sort of feedback from MS. Nothing worse than having a forum to provide feedback but not getting any from the organization. Such poor customer service. MS no longer has a monopoly on office related products. Either get with it or people will sue something else.

    BTW - I have the same issue as everyone else on this thread.

  • J. Schmidt commented  ·   ·  Flag as inappropriate

    Please bring back the document panel, our organization uses this with SharePoint. The workflows have gotten significantly more complicated for users.

  • Dave Wright commented  ·   ·  Flag as inappropriate

    My whole division counted on this feature to Automatically file documents in a portion of our SharePoint. It was a customer communication email that would include an attached Word Document. If a specific email address was used in the as a CC the attached document would get filed in an appropriate, SharePoint, customer files location. The Word Document has custom design SharePoint document filing attributes that categorize the documents in SharePoint. The user no longer has access to these properties to accommodate this.

  • Margie commented  ·   ·  Flag as inappropriate

    I moved to a new office where they're using Office 365 ... our customer is using MS Office 2013.
    I'm working to make templates for users to work with at both the company site and the customer site. My templates have depended on the Document Properties panel. (BTW, if I add the Document Properties icon to my Quick Access Toolbar, the icon does absolutely nothing in Office 365. In Office 2013, it opened the Document Properties panel.)

    It totally amazes me that MS takes away functionality that expert/super users have both become accustomed to and depend on!

    BRING BACK THE DOCUMENT PROPERTIES!

    Along the same line ... I have a laptop at home that I will NEVER get rid of because it has MS Office 2003 on it! Why, you ask. Well, MS in your infinite "wisdom" when deploying Word 2007, took away (and have NEVER GIVEN BACK) the ability to create custom buttons and custom button bars.

    Thus, I create templates at home with custom buttons (tied to my styles) and custom button bars. Then, when that 2003 .dot file attaches to a .dotx file, the custom buttons and button bars open in ADD INS ... and it's a LOT easier to get people to format documents consistently with my custom buttons and button bars! You have NO idea the angst that created on my project!!!! My predecessor had created kludgy DOS-like buttons tied to macros that the developers had gotten used to and depended on. Well, along comes 2007 and the buttons don’t work (can’t update them) and a corporate policy disable the use of macros. The developers DEMANDED we give them back their buttons and I kept telling them it wasn’t us … it was Microsoft! Our project was working with a team of MS people and I complained to them ... they investigated ... and said the decision to remove was because they determined that people weren't using the feature! It got really, really ugly. I had an idea to try creating a TestTemplate at home with my Word 2003 with five custom buttons tied to styles and brought it to the office, not expecting it to work. To my amazement, the custom buttons opened in ADD INS. I was given permission to recreate the developer’s template at home with custom buttons/button bars and deploy it to the project. The developers were finally happy … and I saved my job!

    WHO makes these horrible decisions??
    When you took away the custom buttons/button bars in 2007, WHO did MS check with? I am prone to suspect it was more likely some young, inexperienced MS new hire who didn't understand the functionality or why anyone would use it and said ... let's get rid of it.

    You NEVER gave back the custom button bar feature ... which makes my life a nightmare. I have to create the buttons/button bars at home ... bring them in to work and try them out ... if they don't, I have to take copious notes of what I need to fix ... go home and "fix" and try again until it works. I’m not the only EXPERT Word user who complained about MS removing this feature.

    So, now you've done it again! You took away the Document Properties panel ... will you EVER give THIS functionality back to us?? (The solution to access Advanced Document Properties, reminds me of the Word 2003 and earlier versions of the dialog box that NO one used or wanted to use. To get to Advanced Document Properties is also a LOT more keystrokes. My users will never do that.) The Document Properties panel is attractive and easy to use … and easy to explain to my users.

    Give us BACK both the Document Properties panel and the CUSTOM BUTTON functionality!!
    PLEASE!!!!

  • Gene commented  ·   ·  Flag as inappropriate

    Not saying anything that hasn't already been said. Bring document panel back please.

  • Rhea commented  ·   ·  Flag as inappropriate

    Please bring the document panel back - this is a hindrance in the way we do business.

  • Josh commented  ·   ·  Flag as inappropriate

    To clarify re comments below... I am referring to Managed Metadata fields specifically. I can edit a Single line of text field within the document just fine.

Feedback and Knowledge Base