You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The -OutputFormat ManagedPropertyMappings flag does appear to pull back the Refinable properties, but does not include all of the other managed property attributes.
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 theGet-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.
The text was updated successfully, but these errors were encountered: