Forum Discussion
PnP Modern Search v4 multitext column search on a non queryable managed property
In order to use PnP Search, i tried to map a crawled property into the Refinablestring managed one, however all of them does not have or allow to use the "queryable" property.
Results in Copilot and GPT prompts say it should be checked, already tried to change in the site collection and in only one site. When i tried to create a new managed property, couldn't make it "refinable" but "queryable" was available for selection.
The use of the filtering in the PnP Search would be:
- (1)One Sharepoint library with choice and text columns filled with metadata regarding PDF documents from my org, like tecnical notes, laws, etc. This one is intended to have some kind of search inside the doc too.
- (2)One Sharepoint list that would contain a text column with entire sections of a manual and a column with the sharepoint link to it inside a page. Expected behavior is: User types text -> Finds section -> Redirection.
This manual is stored in SP Online as a page with collapsed sections and has lots of images and text, so it probably will be moved into more than one page shortly, the links are generated when the text webparts get some kind of "Title" on it. Its also on a PDF and thats roughly 500 pages now.
The PnP webparts used are search, search verticals and search results.
Any ideas if i can make the Refinablestring queryable or create a new property thats refinable?
1 Reply
Hi Thiago911
you can map automatic created crawled properties to existing RefinableStringXX managed properties in SharePoint Admin Center. After that you can use the properties for your search cases. As alternative you can create your own managed properties.
But take care, currently MS have a known issue with crawled properties and theire mapping, a fix will be rollout in the next weekes WW (=world wide):
https://github.com/microsoft-search/pnp-modern-search/discussions/4946
Best, Dave