[FEATURE] Get-PnPSearchConfiguration support for Refinable managed properties
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 904
- Forks
- 407
- Avg merge
- 9h 16m
- Merged PRs (30d)
- 10
Description
Describe the solution you'd like
Get-PnPSearchConfiguration currently returns all custom managed properties. Unfortunately, while this would have been sufficient for on-prem SharePoint, any time you need properties to be refinable or sortable in SPO, you have to map crawled properties to the existing refinable managed properties (e.g., RefinableString00, RefinableDate19). I would like for the Get-PnPSearchConfiguration to be able to retrieve any of these properties that have mappings.
Describe alternatives you've considered
There is no other alternative that I've found. There does not appear to be any way within Graph or SPO REST to retrieve managed properties.
Additional context
I'm attempting this as part of a broader attempt to use Microsoft 365 DSC, which utilizes PnP.PowerShell.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Get-PnPSearchConfiguration cmdlet and review the SharePoint search-schema guidance linked in the issue. Compare its current handling of custom managed properties with mapped RefinableString and RefinableDate properties. Done means the cmdlet can retrieve refinable or sortable properties that have mappings, supporting the Microsoft 365 DSC use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100