Hi,
with Word 2016 the document information panel is gone so now I divert customers to set custom property values in Info -> Properties. Some customers but not all are having problems setting the properties. They create documents in SharePoint online document library through a custom Content Type, the document opens in Word and they have to fill out required custom properties. We don't use lookup columns anymore in document Content Types because they don't work in Office 2016, so we use managed metadata columns instead.
When some customers (not even all within one company) create a document from a Content Type and open Info in Word 2016 for that document to set the properties a pop-up window opens that refers to the document library. In that window they have to choose a Content Type and some properties appear when they do so (not all of them, not even some that are required). They have already chosen the Content Type in SharePoint online and shouldn't have to choose it again in Word. But even though they set the property values in this pop-up window the values don't stick and the customer can't save the document and check it in for the first time. Workaround is to close the document, go to Edit Properties for that document in SharePoint and there set all values, save and then check in. They shouldn't have to do that.
Are there any problems going on in the SharePoint O365 environment, with all the changes and updates to the look of libraries and forms that have been going on?
There are only two columns that are displayed in that pop-up window but there are many more and others that are required. Can anybody tell me why this is happening? Is there something interfering with the connection between SharePoint online and Word 2016? All these customers have Office 2016 and sometimes the person next to the one having this problem is not having a problem like this at all and can fill in all the properties, save and check in. So some people are having this problem and some are not. Might it be the installation of the Office 2016 package on these machines or is it something else? This is really bad and can cause people to not want to use O365 SharePoint.
If anybody has any suggestions or can point me to the right direction I would be really grateful.