Power Apps can now display images from Microsoft Lists | 365 Message Center Show 196

preview_player
Показать описание
Use the images stored in a Microsoft List and surface them in Power Apps. Create apps that help frontline workers. Use a Microsoft List in the back end to manage the content, now with images. New apps that use the SharePoint connector to add a list as a data source may display images from the list if they are present in the list.

In this episode:
0:00 Intro
4:13 Customize the properties for the Yammer Communities app in Teams
8:10 Power Apps can now display images from Microsoft Lists
10:48 Headspace mindfulness content in Microsoft Viva Insights is here
14:38 Microsoft Search Usage reports for Modern Site Collections

📢 Quick mentions - short updates and reminders to prepare for major updates
19:54 (Updated) Microsoft Teams: Dynamic View
21:04 Internet Explorer 11 (IE11) desktop application retires on Windows 10
22:59 Sharing Links for Microsoft Lists is now available!
23:45 Outlook - Changes in how feedback is submitted

📞 Call back - Discuss one or two updates that we've covered in older episode, which are arriving in tenants.
25:05 Set out of office within Microsoft Teams
29:31 New Teams meeting lobby setting - only invited users join directly

33:01 Outro

Join Daniel Glenn and Darrell as a Service Webster as they cover the latest messages in the Microsoft 365 Message Center.

Check out Daniel and Darrell's own YT channels at
Рекомендации по теме
Комментарии
Автор

Just wondering if the function to display List images had been published yet? Can't find much information on this after the proposed June release.

nikitaluo
Автор

Great info, guys! However, to clarify one statement that was made, the images in an image column are not stored IN that column. They're dropped into the "Site assets" library in the site. The image column type is just a "hyperlink" column with the display option permanently set to "picture". The ability to use them in Power Apps from that list is cool and cleaner than the wacky workaround I found (store them in a separate doc library with a "related item ID" column to allow filtering).

cvkealey