Forum Discussion
News Web Part Filter Not Available
- Jan 05, 2019
I think the ability to filter on news across site collections is supposed to be coming at some point. What you can do now is use the Highlighted Content web part to pull in news articles from multiple site collections and then filter on a managed property. When I need to do this, I create a managed metadata property that I use on all of the sites I want to roll up and then map each property to an available managed property in the search schema (e.g. RefinableString05). Then I can filter the news based on that shared property - but for now, only in the Highlighted Content Web Part.
I think the ability to filter on news across site collections is supposed to be coming at some point. What you can do now is use the Highlighted Content web part to pull in news articles from multiple site collections and then filter on a managed property. When I need to do this, I create a managed metadata property that I use on all of the sites I want to roll up and then map each property to an available managed property in the search schema (e.g. RefinableString05). Then I can filter the news based on that shared property - but for now, only in the Highlighted Content Web Part.
- M365061290Jan 08, 2019Iron Contributor
Does alias name appear in high lighted content webpart or you need to use RefinableString
- Susan_HanleyJan 08, 2019MVP
You need to use RefinableStringxx.
- dmowryJan 08, 2019Brass Contributor
So with On-Premise I could add my custom column to the Search Schema and be able to use the property in my filters as a Managed Property. Is this no longer the case and I have to use the RefinableString fields now?
- dmowryJan 07, 2019Brass Contributor
The trouble I have with Highlighted Content is that it doesn't provide the same layout options as the News web part. Is there anyway to add layouts to the highlighted content web part?
- SusanHanleyJan 07, 2019MVPNot at this time.
- dmowryJan 07, 2019Brass Contributor
As I am moving our intranet to SharePoint Online and trying to keep consistent functionality from SP2013 and SharePoint Online, the phrase "Not at this time" is becoming way to common. By the time I'm done I may have more custom code on this site than I would like, which means I have to manage this while MS gets the features I need added.
Nothing anyone (but MS) can do, I know, but still frustrating.