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.

657 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    267 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • peter martensen commented  ·   ·  Flag as inappropriate

        This is one of the worst thought out changes MS has ever done. The benefit to Sharepoint is the metadata. And by deprecating the DIP, MS made entering metadata so much harder. My users are openly revolting against using Sharepoint just for this one reason. And I really don't understand why there's no easy way to ad metadata from Word Online. That should be the easiest solution of all, and it's impossible. You can't even get to Document Properties to add it. I really have to wonder about the choices MS is making. They are losing market share everywhere to everyone on all platforms, and then they go and make something hard to do that people rely on.

      • Randy Moore commented  ·   ·  Flag as inappropriate

        In response to Thaddeus, and to ensure giving no false illusions to the Microsoft team working on it, the success of this solution depends on one's own definition of "it works and works great". It works, yes. But, so far, right up to the most recent build date, it is still plagued with all of the issues enumerated by myself and others below. From my perspective, it is useless compared to the former DIP in 2013 Office and the ability to use InfoPath to create custom DIP solutions.

      • Alan C commented  ·   ·  Flag as inappropriate

        Hi Thaddeus - how can I check which version of O365 we are using? I've sniffed around the Admin side of things, but with no success to discover this. Any help would be very much appreciated. Thanks Alan C.

      • Thaddeus Ferber commented  ·   ·  Flag as inappropriate

        It already works for me, and works great!

        I am on Microsoft Office 365 ProPlus Version 1711 (Build 8730.2165 Click-to-Run), Monthly channel, signed up for first release.

      • Alan C commented  ·   ·  Flag as inappropriate

        Hi, I just wondered if anyone (notably Chris D from below) had heard if the January 2018 date for release of this feature was still likely to happen? I'm particularly interested to discover if this is available for Office 365 as we have a project on hold until this capability is freely and fully available.

        Any news would be gratefully received. Alan C.

      • Jean-Pierre Huls commented  ·   ·  Flag as inappropriate

        Please apply to Excel as well. No matter how great SharePoint/O365 is, there are still a lot of users out there using spreadsheets (templates) to store data along with (complex) calculation into SharePoint/O365 and being able to edit SharePoint metadata in Excel is as essential as it is for Word 2016.

        NB: odd to notice that the SP metadata window pops up in Excel (and probably Word) 2016 for files with populated metadata and not for newly created files (Library/Files/New Document).......

      • Andrew Bragan commented  ·   ·  Flag as inappropriate

        I’m hoping that this is a work in progress because at the very least the final solution needs to behave like the DIP did in Office 2013.

        As I noted in my first post back in 2015, the original DIP allowed the use of standalone templates i.e. not hosted on SP. These were used to create new documents that immediately opened the DIP, which allowed users to quickly enter metadata that was reused in Content Controls throughout the documents. Further, when documents were uploaded to the SharePoint library, the data in these fields was shown in the library list view.

        With version 1710 (Build 8625.2121) this is not happening. When using a standalone template, the DIP does not seem to be supported. Clicking on View Tab>SharePoint Group>Properties just takes me Backstage.

        Admittedly, the DIP is available when opening a document from an SP library, but it must be done manually and is very slow to open. The Subject field does seem to be broken however, as when the document is saved back to the SP library the content of this field is not uploaded.

        Unlike the Title field, there appears to be no link between the SP Subject field and the Document Subject field.

      • Randy Moore commented  ·   ·  Flag as inappropriate

        In Office 2016, with removal of the Document Information Panel (DIP) and the ability to use InfoPath to customize the DIP, we lost a great deal of control, function and flexibility for leveraging data across SharePoint lists, and for customizing the properties and metadata that we need to have associated with our SP documents. Our organization relied on a customizable DIP in very substantial ways. It was good to see Microsoft finally respond with plans for a replacement. However, so far, the solution is sorely lacking in the following ways:

        1. The document properties panel does not open upon creating a new document from a SharePoint library. This is the case even when enabling the SP content type setting to have it do so. The document first must be saved to open the panel. This causes a conflict if a SP property column is set to “required”. The document will not save to the library because the required property is missing. To make matters worse after the save is attempted, the panel will appear, but it shows “No SharePoint properties found”. This leaves the user without the ability to enter the required property and stuck not knowing what to do next.

        2. As is, SharePoint Lookup columns are a poor substitute to using InfoPath for creating connections to SP lists. The list and the library must reside on the same subsite. Lookup columns cannot be set on lists on another subsite in the same site collection. This forces large lists and large libraries to reside on the same subsite.

        3. Lookup columns cannot be configured to filter data, or include other data from other fields in a list based on selections made in linked fields. This functionality may never be possible with SP lookup columns, but if the other issues listed here are not addressed, the lookup column will be useless and render the new document properties panel pointless for us.

        4. When a property is derived from a lookup column, the actual contents from the SP list column (e.g., all client names) will appear in the properties panel as choices in the dropdown control. So, if I select Jane Doe, “Jane Doe” appears in the dropdown control in the panel. However, if I use Quick Parts to insert that same document property into the document itself, it returns the list item ID number (e.g., it returns “234”, which is Jane Doe’s item ID number in the SP list). That is not useful if I have a Word template that uses the document properties for composition purposes.

        5. Even when a lookup column is set in SP to include other columns (fields) from a SP list, those additional columns are not included in the SP properties panel in Word. But, what’s worse is they are not included as document properties in the Quick Part fields in Word. (The associated columns show in the SP library, but not in the SharePoint properties of the document itself.)

        6. We need to have all of the associated lookup fields available as document properties while creating documents based on SP content type templates. For example, if I’m composing a form letter, and I pick the client “Jane Doe” from my SP properties list, I will also want her location, classification, date of last contact, etc. to be included in my document properties so I can insert them into the document and include them as SP metadata.

        Thanks for listening.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I have the latest build and it still doesn't work with a new document.
        Shows "No SharePoint properties found"
        Can't change the properties for a lookup field since "show information" doesen't work.

      • Lawrence Dwight commented  ·   ·  Flag as inappropriate

        Any documentation on this? I have the panel, but it says "No SharePoint properties found". What do we need to do on the tenant side for this to work?

      • David commented  ·   ·  Flag as inappropriate

        We tried the new solution and while it looked nice with at form on the right of the document in Word it totally missed the mark. Here is why:
        • It only works in Word and with SharePoint online
        • The form cannot be shown before the document is saved which makes it useless since the ability to fill in metadata as you save a document for the first time is most of the point of the DIP. Also this makes it impossible to save a document if there is a required field.
        • The form does not appear automatically on a new document (well how could it when it can’t even show if the document haven’t been saved).

      • Anonymous commented  ·   ·  Flag as inappropriate

        I am trying to access an older Word document. Although I can open it in Word 2016, part of the table is missing. What can I do to get the text contained in that part back?

      • Scott Joyner commented  ·   ·  Flag as inappropriate

        The was functioning briefly this week and now seems to be turned off. I have the ability to view the new document panel, but it is not showing the SharePoint properties assigned via the associated content type. Also the AutoSave button in the quick access tool bar is greyed out and it says it is 'not available'. Any thoughts on when this will be working again? I'm on version 1709 Build 8528.2139 Monthly Channel

      • Anonymous commented  ·   ·  Flag as inappropriate

        I need the possibility to directly access the extended property panel via the customized panel. Importing the "Wordxxx.exportedUI" from word 2010 doesn't work. This is really a downgrade of functionality!

      • Max commented  ·   ·  Flag as inappropriate

        I recently saw this functionality live - multi person and managed metadata fields supported! Cannot find the property button myself though, probably not in my tenant...

      ← Previous 1 3 4 5 13 14

      Feedback and Knowledge Base