Forum Discussion
Marc Mroz
Microsoft
MicrosoftRolling out - Custom thumbnails & title & description metadata
We started rollout of new capabilities to video and audio files stored in SharePoint, OneDrive, Yammer, and Teams allowing you to set a custom thumbnail for a video as well as set the title and descr...
Marc MrozMicrosoft
MicrosoftTitle should show up in various places. And description I believe can be added from classic library settings??
But we haven't put effort into making them show up in all the places. Do you have ideas on hat we should do and how you'd use it?
But we haven't put effort into making them show up in all the places. Do you have ideas on hat we should do and how you'd use it?
Hi Marc, thanks for your reply! You're right, Title shows up - apologies, I missed that somehow.
Description though seems to be a bit more elusive. I can get it to display is on the All Documents view as a column but then on the details pane the Description field is missing.
On a custom view, Description is selected as a displayed column, but in the Document Card Designer the column isn't available for selection. Again, missing in the details pane.
Description though seems to be a bit more elusive. I can get it to display is on the All Documents view as a column but then on the details pane the Description field is missing.
On a custom view, Description is selected as a displayed column, but in the Document Card Designer the column isn't available for selection. Again, missing in the details pane.
- Just in case anyone else is searching for a similar issue, I stumbled across the solution:
1 In the library's settings, the column Description has to be added to the content type in use (in my case, called Document). The field should now be available for other library views e.g. gallery.
2 If you want to refer to it in JSON formatting, again on the library settings page, looking at the URL for the column name Description in the list of fields reveals its name: "_ExtendedDescription"
3 The field can now be used by referring to as [$_ExtendedDescription].
Highly intuitive 😒 ... why isn't this in MS's own documentation? Believe me, I tried in vain to search for it.