View SharePoint Document Properties by default in SPO within Microsoft Word?
Can metadata associated with Word documents in a SPO Document Library be viewable from within a Word document by default (as it was in SPS 2016)? Here’s how it used to work with SPS and how it now works with SPO. Both document libraries are identical (same documents, same metadata).
SPS 2016
1. Open Word document from SPS Library
2. Document content and SharePoint Properties (i.e. metadata) instantly viewable/editable.
SPO
1. Open Word document from a SPO Library
2. Document content instantly viewable. SharePoint Properties are not viewable.
3. Switch to the ‘View’ ribbon
4. Locate the section of the ‘View’ ribbon named ‘SharePoint’ and select the ‘Properties’ button.
5. The SharePoint Properties (i.e. metadata) for that document is now viewable/editable.
Notice how much more efficient the process was in SPS 2016? Any reason Microsoft did not want that process to remain as efficient? is there a different process we should be defaulting to with SPO? For example, is it better to work with metadata outside of the Word document? If not, how can we make this work for SPO like it did SPS16? Is there a setting? Can we submit an enhancement? is there a workaround or hack?
Can metadata associated with Word documents in a SPO Document Library be viewable from within a Word document by default (as it was in SPS 2016)? Here’s how it used to work with SPS and how it now works with SPO. Both document libraries are identical (same documents, same metadata). SPS 20161. Open Word document from SPS Library2. Document content and SharePoint Properties (i.e. metadata) instantly viewable/editable. SPO1. Open Word document from a SPO Library2. Document content instantly viewable. SharePoint Properties are not viewable.3. Switch to the ‘View’ ribbon4. Locate the section of the ‘View’ ribbon named ‘SharePoint’ and select the ‘Properties’ button.5. The SharePoint Properties (i.e. metadata) for that document is now viewable/editable. Notice how much more efficient the process was in SPS 2016? Any reason Microsoft did not want that process to remain as efficient? is there a different process we should be defaulting to with SPO? For example, is it better to work with metadata outside of the Word document? If not, how can we make this work for SPO like it did SPS16? Is there a setting? Can we submit an enhancement? is there a workaround or hack? Read More
