pnp search filter webpart
2 TopicsSite Columns don't become Crawled Properties (in page library)
Hi all, I hope someone here can help me as the admins in my organization don't seem to find a solution to my issue. My problem is this: I have site columns fed by my managed metadata. I use those site columns in document libraries and in the page library. My goal is to filter all documents and news posts using the PnP Modern Search (v4). This works very well so far - at least for the documents inside my document library. For whatever reason, however, when adding site columns to the page library instead and filling them with metadata, these metadata do not become crawled properties, i.e. they do not show up when I try to add them to managed properties (RefinableString). This is really odd and I suppose this is due to incorrect site settings. I was in touch with colleagues from my organization who run another SP communication site and who do not run into this problem, but where page library columns are readily available as crawles properties. Can anyone think of a possible solution? Many thanks!3.9KViews0likes5CommentsDEFAULT SELECTED VALUES in the Pnp search filter webpart
Hello Team, I have a modern page with pnp search results webpart connected to search filter webpart and i want refinement values to be automatically selected at the page load. Can you please advise if this is possible? Below is the screenshot of the refinement values. I tried the below URL parameter under Refinement Filters option in the search results webpart but it doesn't seem to work ?filters=[{"n":"RefinableString05","t":["equals('Congregations')","equals('Parish Missions')","equals('Presbyteries')"],"o":"and"}]2.3KViews1like1Comment