-
Notifications
You must be signed in to change notification settings - Fork 194
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
Support to create crawled and managed search properties #887
Comments
@matsla : There are no individual APIs to create managed/crawled properties, the only API surface we have is CSOM based and allows you to extract the search configuration of a Tenant/Site/Web into an XML file and then using a similar approach that XML file can be re-applied to a Tenant/Site/Web. See https://github.com/pnp/powershell/blob/b85297d68b51008e06bab0901562f2a9b2a75e94/src/Commands/Search/GetSearchConfiguration.cs and https://github.com/pnp/powershell/blob/b85297d68b51008e06bab0901562f2a9b2a75e94/src/Commands/Search/SetSearchConfiguration.cs for the PnP PS implementation. We could include something similar in the Admin library if that can help with your scenario? |
@jansenbe yes this can help out in my scenario. I need to move search configuration on site collection level to a target site collection on a different tenant. |
@matsla : this is in progress, search configuration export methods are already done at tenant/site/web level, the import parts will come soon. |
@matsla : the search configuration can now be exported and imported at web, site and tenant level. Under the covers this is realized by wrapping the needed CSOM APIs, to feature wise this works the same as in PnP Framework or PnP PowerShell. Will be part of the next nightly release and just in time for version 1.7 which we'll release this week. |
Is there any plan to support to create crawled and managed search properties in scope site collection and tenant?
The text was updated successfully, but these errors were encountered: