Build your modern intranet with SharePoint in Office 365 – Microsoft Ignite 2018 announcements

RE: my earlier post

Connecting the dots between this blog post, and another blog post of more announcements from Ignite...

Webpart-to-webpart connections – Let web parts talk to other web parts and your pages and experiences become more dynamic with data and interactive. You will be able to configure web parts to get their property values from other web parts, including updating those values based on what is selected.

 

Initially we will support dynamic data in a few of our 1st-party webparts, with the intent to grow these capabilities through the SharePoint Framework - more and more web parts (talking to other web parts).

Am I coming at this wrong, in expecting to resolve with just the Highlighted Content web part?

Would the fix actually be to combine the Page Properties web part configured to reveal the column we want to filter on, and have that work to limit the scope in the Highlighted Content web part--to have them working together?

Mark-Kashmanwould this be the solution ?

• Scoping the Highlighted Content web part to be all sites
• Setting the Page Property to = the Metadata I want to filter on
• Revealing that meta in the Page Property web part
• Making a webpart-to-webpart connection

If this is the ticket, how's such a broad filter likely to impact performance, anything to worry about there?