search

pnp / PnP

SharePoint / Office 365 Developer Patterns and Practices - Archived older solutions. Please see https://aka.ms/m365pnp for updated guidance
https://aka.ms/m365pnp
Other
1.9k stars 3.31k forks source link

Issues deploying managed metadata field - search is not picking up the Note hidden field. #1809

Open hosoistreet opened 6 years ago

hosoistreet commented 6 years ago

Category

[X] Bug [ ] Enhancement

Environment

[X] Office 365 / SharePoint Online [ ] SharePoint 2016 [ ] SharePoint 2013

Expected or Desired Behavior

We have deployed several managed metadata fields via XML pnp provisioning script. After deploying the managed metadata field, uploading content into the field, checking in the content and publishing and finally running the search re-index, we should be able to run search queries using the ContosoOwningFunction_Note generated managed property. (This is equivalent to the owstaxid... managed property, its just called something different within our XML.

Observed Behavior

The managed metadata field is deployed with no errors.

The field value can be set ok on content and we can search on items using the taxonomy field but we are unable to perform queries against the note field. No ContosoOwningFunction_Note managed property is generated after reindex\crawl. Furthermore no crawled property has been generated either for this note field.

These are important as allow use of TERM GUIDs in queries.

Steps to Reproduce

Create a managed metadata field using the following code. This creates the note field and a corresponding taxonomy field.

Using SharePointPnPPowerShellOnline 3.0.1808.1

`

SspId {sitecollectiontermstoreid} TermSetId {termsetid:Contoso Corporate:Functions} TextField {ddc50a26-763b-67c7-4937-5011f1cbc34f} IsPathRendered false IsKeyword false `
phillipharding commented 6 years ago

@hosoistreet there's a simlilar thread on the provisioning schema repo, which may help.

https://github.com/SharePoint/PnP-Provisioning-Schema/issues/49#issuecomment-272532305

hosoistreet commented 6 years ago

@phillipharding Thanks Philip, that's the same issue however we need to be able to fix the fields as they exist in a production environment. Creating new fields and copying the data across is not an option. Probably more a question for Microsoft, to see if they are able to fix corrupted metadata fields that do not get picked up in crawls.