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.
Microsoft released an update for 2016 office that stated the following:
"This update enables the Document Information Panel feature in Office 2016. After you install this update, you can update the SharePoint and document properties of an Office document by selecting the View tab, and then clicking the Properties button that will open the Properties panel."
Has anyone been able to get it to show? We have been unsuccessful.
It doesn't work in 0365 either.
Since Microsoft are too lazy to provide an update and everyone here is in the same boat my organisation was in, I will summarize & paraphrase what our Microsoft account manager told us. This is based on information provided to him internally, valid as of March 2018.
There is no further development taking place on this, and there are no current plans to bring it to Office 2016. Essentially, using Office 2016 means settling for File > Info > Properties, buying a 3rd party product, or developing a custom solution.
My personal opinion is that this is a ham-fisted attempt to move people to O365 but I don't know why Microsoft doesn't simply update the answer instead of leaving everyone guessing, in some cases deferring upgrades. To say their handing of this has been unhelpful is an understatement.
Ricardo Diaz commented
Any news on this front?
i can only say i am disapointet about the way they work and now after we trustet funktions are available now gone we do documentation with consitent Content was a pretty function and reliability on . so we can not relay on funktions on Office what makes not a smart application anymore.
HummusFan 123, you sir are the William Shakespeare of comment threads. Hilarious... and Totally right!
Can you please provide an estimated timeline
HummusFan 123 commented
I imagine the gods of whichever pantheon created humanity experienced a similar existential crisis as that which our friends at Microsoft are going through now. So powerful, ubiquitous, successful and rich, both physically and spiritually, the gods realised they were bored and created a spark that bled down the mountains and became the first humans.
Microsoft seem to be suffering the same boredom now, but instead of creating new and beautiful things, they are creating dismay, distraction, and disfunctionality, while they remove all that the universe currently holds dear. Perhaps if Microsoft had modelled their creations off sensible, adaptive, evolution instead of the arbitrarily edictatorial word of a long forgotten god, we'd not be in this situation.
Microsoft appear to be so bored with the world they created, they are behaving like that kid in school who built the perfect sim city game, only to release every single disaster all at once, just to see what happens. It's even worse than that though. They are like the kid in school who logged on to the shared computer and opened MY perfect sim city game and then released every single disaster all at once, just to see what happens. I haven't forgotten you, Andrew Porter, and I never will. The same shall be said of Microsoft and their deprecation of a document information panel so core to finally making sharepoint work in our organisation...in any organisation...that I will never forget them either.
And don't forget what happened to Maxis, the producers of Sim City. They were subsumed be EA, and we all know what happened there. An example of another company who prided their own transactional agenda over customer satisfaction and usability. Don't be Maxis. Don't be EA. Don't be Andrew Porter.
Nobody likes InfoPath. I get it. InfoPath was tired. It was inaccessible. It was only half executed. But it was sent to death row years ago without replacement. Now, years further on you've rolled the tanks into the last little InfoPath enclave to eradicate all traces of your embarrassing rebel progeny from the earth. Cool. Except, like, what are you replacing it with?
To pride Infopath's destruction over functionality retention is ludicrously misguided. To have this issue go TWO YEARS without even a promise of address is the worst example of customer service since Seinfeld Episode 116. But "NO METADATA FOR YOU" doesn't sound the same without Larry Thomas' Yev Kassem character shouting it. Newman wanted his Jambalaya and I want my damn document information panel. You want it to look cool and modern and not use InfoPath? Great, but let's solve that first before we kill it.
Apple don't call a press release to announce the iPhone 8 is end of life and then slowly and non-committally answer questions by stating that the iPhone 9 is not on the roadmap.
Ford don't remove something as fundamental to their customers as a steering wheel only to say "that's not on the road map." You can't even stay on the road without a steering wheel, so what good is a road map? Plus we have Google maps, so who needs a bing based road map anyway? Google. They love deprecating features. They also love providing accurate mapping and search results though, so you can't really model Google in the bad unless you do so in the good.
When Donald Trump gets behind the amazing new F-35 fighter project, despite it being a project that has been so expensive, polarising, and drawn out that it makes the performance of MS Teams seem positively athletic. He gets behind it, sure, but he doesn't get rid of all the old fighter planes upfront, does he? That would be stupid. That would be dangerous. That would be the Microsoft way of running a country.
Speaking of running a country, and Donald Trump, remember the allegations about Russian bots retweeting Trump to win the election? Yeah, wow, controversial. Looking at this thread, it sounds like we don't even need bots to make our voice heard, because you've done what trump couldn't: mobilising angry voters unaided.
I'll try to set this out in words everyone will understand: This whole document information panel is like Hummus.
Everyone likes Hummus. Everyone.
Some people like Crab Dip. Some people like Eggplant Dip. Some people like Onion Dip, Some People like Caviar. Everyone likes Hummus, though.
I know this analogy, even before I complete it, has the product development team salivating both at the promise of hummus and the potential to ruin hummus for everyone, but hold tight, let's just think about how they might ruin hummus:
"I know! Let's make a hummus with CRAB and EGGPLANT and ONION and CAVIAR and add them to the Hummus!"
"But what if we just made five differe..."
"Shutup, you're fired! As I was saying, we've now got this super Hummus. It's only available via subscription."
The garlic, tahini and chickpea features were deprecated from Hummus later that day. The Hummus post on user voice was the largest ever.
Microsoft seem to be living in a Benjamin Button universe since every new product generation is slower, buggier, uglier and less user friendly than the last. What a ridiculous decision to remove the DIP before a replacement is available.
[Deleted User] commented
Please release this!!!
Dean Gross commented
it has been many months, where is the fix?
Shawn McTaggart commented
Adding to the chorus: When will the fix be available? Office 2016 has made our existing SharePoint workflows utilizing Content Types and required fields nearly unusable!
Echo other users - when is the release going to be available? The existing workarounds are not satisfactory.
when is the final release for this add-on? and we need it also in Excel and PowerPoint.
Ray Boone commented
Yeah--just tested here and same thing...doesn't work for required lookup columns. I can at least see the options in the columns but selecting them still doesn't allow for saving back up to the document library.
Gareth Burrows commented
It "kind of" works... It does not work for lookup columns, which are set as required fields. All other types of column seem to work correctly, but not for a lookup column. You get stuck in the save document/property required loop. This does not happen when using sharepoint 365 and creating the document using word online, as word online appears to ignore the validation (required field) and saves the document with the metadata being left blank.
peter martensen commented
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
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.