Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get-PnPSearchConfiguration seems to return only a subset of managed properties #4743

Open
5 tasks
jasmeeners opened this issue Feb 18, 2025 · 0 comments
Open
5 tasks
Labels
bug Something isn't working

Comments

@jasmeeners
Copy link

Notice

Many bugs reported are actually related to the PnP Framework which is used behind the scenes. Consider carefully where to report an issue:

  1. Are you using Invoke-PnPSiteTemplate or Get-PnPSiteTemplate? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/pnp/pnpframework/issues.
  2. Is the issue related to the cmdlet itself, its parameters, the syntax, or do you suspect it is the code of the cmdlet that is causing the issue? Then please continue reporting the issue in this repo.
  3. If you think that the functionality might be related to the underlying libraries that the cmdlet is calling (We realize that might be difficult to determine), please first double check the code of the cmdlet, which can be found here: https://github.com/pnp/powershell/tree/master/src/Commands. If related to the cmdlet, continue reporting the issue here, otherwise report the issue at https://github.com/pnp/pnpframework/issues

Reporting an Issue or Missing Feature

Expected behavior

After calling Get-PnPSearchConfiguration -Scope Subscription -OutputFormat CompleteXml , converting the results to an xml object, and viewing this property: $xml.SearchConfigurationSettings.SearchSchemaConfigurationSettings.ManagedProperties.dictionary.KeyValueOfstringManagedPropertyInfoy6h3NzC8, only 11 managed properties are available.

I would expect that this object should contain all managed properties in the search schema?
Although there is no documentation at all on this cmdlet with the exception of:
"Returns the search configuration"

is that a bug? or by design? is there anyway to retrieve ALL managed properties in the search schema?
why is this subset returned?

Actual behavior

in my case this only returns 11 managed properties. I am not sure why these particular managed properties were selected?

I would like to retrieve ALL managed properties in the search schema.
Also, it would be very useful if the cmdlet documentation referenced any documentation on the structure of the schema object that is returned.

Steps to reproduce behavior

step 1. connect to https:\tenant-admin.sharepoint.com

$clientID = "myclientID"
$site = "https://mytenant-admin.sharepoint.com"

Connect-PnPOnline -Url $site -Interactive -ClientId $clientID

step2. $searchConfig = Get-PnPSearchConfiguration -Scope Subscription -OutputFormat CompleteXml

step3. [xml]$xml = $searchConfig

step 4. examine this object $xml.SearchConfigurationSettings.SearchSchemaConfigurationSettings.ManagedProperties.dictionary.KeyValueOfstringManagedPropertyInfoy6h3NzC8

in my case only 11 managed properties are returned. I am not sure why these 11 are returned. I would like to get ALL managed properties in the search schema, so I can filter them. Perhaps there is a reference somewhere to more comprehensive documentation on the data that this cmdlet returns. it doesn't seem to be the entire search schema.

it seems like there is lots of useful information returned, but it would be helpful if there was some sort of reference to understand what is being returned.

What is the version of the Cmdlet module you are running?

2.12.0
(also tried with latest nightly build 2.99.138 )

Which operating system/environment are you running PnP PowerShell on?

  • [x ] Windows
  • Linux
  • MacOS
  • Azure Cloud Shell
  • Azure Functions
  • Other : please specify
@jasmeeners jasmeeners added the bug Something isn't working label Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant