Sharepoint Online Refinablestring not allowing "queryable" property

Question

Sharepoint Online Refinablestring not allowing "queryable" property

Thiago de Freitas Ribeiro 0

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.

Any ideas if i can make the Refinablestring queryable or create a new property thats refinable?

0 comments

1 answer

Your answer

Answer 1

Dear @Thiago de Freitas Ribeiro,

I hope you’re having a good day.

Based on your description, I'm not convinced that the missing Queryable setting is necessarily the root cause of the problem.

What stands out is that you're trying to use a crawled property with one of the built-in RefinableStringXX managed properties. At the same time, you've noticed that:

RefinableStringXX properties do not expose the same configuration options as custom managed properties.
A newly created managed property allows Queryable, but cannot be made Refinable in the same way as the built-in refinable properties.

From your description, this behavior appears consistent with how SharePoint Online exposes predefined refinable managed properties versus custom managed properties.

Before focusing on the Queryable checkbox itself, I think the more important question is how you intend to use the property in PnP Search.

For example:

Are you trying to use the property in a PnP Search Filter/Refiner?
Are you trying to use the property in a KQL query?
Or are you trying to make the field searchable through a search box experience?

The reason I ask is that the required managed property characteristics differ depending on the scenario. If your goal is filtering or refinement, the built-in RefinableStringXX managed properties may already be the correct approach, and the inability to enable Queryable may not actually be preventing the solution from working.

Could you share a bit more about the specific PnP Search configuration you're building and what you're ultimately trying to achieve? That will help determine whether Queryable is truly required or whether the issue lies elsewhere in the search configuration.

Please understand that our initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.

Looking forward to hearing back from you with any updates or additional details.

Warm regards,

Thiago de Freitas Ribeiro 0 Reputation points

2026-09-17T16:38:41.8033333+00:00

Hi Liora, thanks for the reply, the use of the filtering in the PnP Search would be:

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 seatch inside the doc too.

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 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.