Forum Discussion
Data Entry in the Document Library
- Hi All,
Thank you for your reply and suggestions. Currently found a workaround with this issue using the ListView Formatting.
Thanks!
Anj 🙂
JohnDayQA and @Anj Cerbolles
The Classic view will indeed have a limited life expectancy.
Do keep in mind that the property promotion of embedded document properties to SharePoint columns has limitations. For example, this only works for Office documents and tiff files. It does not work for pdf files, emails, zip files, drawings, videos, images, ... You also do not have control over the naming of the SharePoint columns, they need to match with the property names in the document. It is also not possible to use multiple document content types in the same library.
Paul
"Do keep in mind that the property promotion of embedded document properties to SharePoint columns has limitations. For example, this only works for Office documents and tiff files. It does not work for pdf files, emails."
I think you are referring to "custom columns". Microsoft have provided site columns that "data map" to Microsoft Outlook messages, contacts and tasks, plus many media applications. A custom Column can map to PDF and other metadata providing the column name you give matches the metadata name. We have proven this to be true in our training courses for over a decade. The first name you create is the name given to the column (or the field parameter in the URL Path if you click and edit the column and look at the very end of the URL properties). Renaming only changes the friendly name seen not the localised name. This is the same with SharePoint apps. It is how the managed properties are defined in the content database.