Forum Discussion
Nov 21, 2017
SharePoint Search
Today my customer reported an issue with search in SharePoint Online. They have a search box web part, a search result web part and a refinement panel:
RefinableString00 is mapped to a Client C...
- Nov 21, 2017
Just to complete this issue. I've created a PowerShell script that touches all the list items in my site collections, so that search will pick up these items. Problem resolved for me! Not sure how this customer got into this situation though.
The script can be found below:
$cred = Get-Credential -Message "Password" -UserName admin@mytenant.onmicrosoft.com Connect-PnPOnline -Url https://mytenant-admin.sharepoint.com -Credentials $cred $sites = Get-PnPTenantSite | where { $_.Url -like "https://mytenant.sharepoint.com/teams*"} foreach ( $site in $sites) { Connect-PnPOnline -Url $site.Url -Credentials $cred $web = Get-PnPWeb $list = Get-PnPList -Web $web | Where { $_.Title -eq "MyList" } $listItem = Get-PnPListItem -List $list $listItem.Update(); $web.Context.Load($listItem); $web.Context.ExecuteQuery(); $listItem }
Mikael Svenson
Nov 21, 2017Steel Contributor
This is not necessarily weird. If you have a regular list column, and map the crawled property for this column to RefinableString00, you effectively remove the content in that column as being full-text searchable. RefinableString00 is not a searchable managed property.
If it's a site column, you should get the same results as the ows_q_col crawled property is searchable, while you map the ows_col and make it non searchable.
I have a table at http://www.techmikael.com/2014/07/what-makes-sharepoint-column-searchable.html which shows how this works.
Nov 21, 2017
HI Mikael Svenson,
that is what I originally thought too as I inspected the RefinableString00 property. But Then I wouldn't have expected the "RefinableString00:XYZ123" to give the correct result either. Unless of course searching for "RefinableString00:XYZ123" isn't considered to be searching.
also the crawled property is marked as
- Mikael SvensonNov 21, 2017Steel Contributor
Correct, mp:something is a property query, not full-text search. Full-text(free text) search is the searchable property, while a property query is the queryable property of a managed property.
- Gregory FrickApr 17, 2018Steel Contributor
Thanks Mikael Svenson ! Your responses are helpful and clarify a complex topic.
- Vivek JainMar 13, 2018Iron Contributor
I have a very minor naive query. In my SharePoint Online library, I have a Power Point document in which it has a text box with value "SCOPE-068-T-CMS101-2017-v1.0". If I do a SharePoint search with "full value" then the search correctly shows the document in search list. But if I search with a partial value say "SCOPE-068-T-CMS101-2017" then it doesn't show the document in search results.
Is there some search setting which can control this behavior? Thanks for the help.
- Arin RoyApr 17, 2018Brass Contributor
Hi Vivek,
It seems that this is related to word breaking or Tokenization capabilities of SharePoint search. If I test with the same text as you have, I see that with the partial query and using wildchar, the highlighted hit on the match is always before the dot.There were tokenization properties announced last year for SharePoint Online last year.
See: https://blogs.technet.microsoft.com/beyondsharepoint/2017/06/17/search-extended-word-breaking/
However these are only available for custom managed properties. In this case, what you didn't mention is whether you use full text search or a custom managed property. I hope the link here can point you to the right direction.