Question

Heley on Fri, 05 Aug 2016 11:01:26


We want to set up a refiner for DetectedLanguage, however this managed property cannot be altered. So our plan was to create a new managed property and map this onto the ows_q_TEXT_TranslationLanguage crawled property, thus mimicking the DetectedLanguage managed property. However, I am a bit cautious on this because I assume that the DetectedLanguage was made non-refinable for a good reason.

Will our approach work? Or is there is a hidden gotcha waiting to happen.


Sponsored



Replies

Shivasharanappah on Fri, 05 Aug 2016 11:40:21


Hi Heley,

As per my understanding All automatically SharePoint created managed properties by default “refine” will be disabled we can edit the managed properties can enable the check box. 
Else you can map to a set managed properties which are available as a refiners but are not mapped to any crawled property( RefinableString00 – RefinableString99) you can use them and i think there is no harm in doing it refineable.

Thanks,
Shiva

Heley on Sat, 06 Aug 2016 07:10:24


It would appear that there is something special with the ows_q_TEXT_TranslationLanguage crawled property ... or something broken with it.

I can see the information in the DetectedLanguage managed property by outputting it in a display template, so I know that the ows_q_TEXT_TranslationLanguage has data in it.

However when creating custom managed properties and mapping ows_q_TEXT_TranslationLanguage onto that property, there is no information in the new managed property. This is, of course, after a full crawl.

I have also found the managed property "languages" which does not map onto any crawled properties and yet appears to have all of the detected languages within a document. Maybe we need to use that.

Chris yuri on Mon, 08 Aug 2016 06:24:53


Hi Heley,

If the DetectedLanguage” managed property has data, You can set it as refinable.

Central Admin->manage service application->search service application->search schema->DetectedLanguage->Refinable-> Yes-active, then you can add it to search result page.

Here is a link about how to add refiners to a search result page:

https://blogs.technet.microsoft.com/tothesharepoint/2013/11/10/how-to-add-refiners-to-your-search-results-page-in-sharepoint-2013/

Best Regards,

CY


TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


Heley on Mon, 08 Aug 2016 07:37:23


Hi Heley,

If the DetectedLanguage” managed property has data, You can set it as refinable.

Central Admin->manage service application->search service application->search schema->DetectedLanguage->Refinable-> Yes-active, then you can add it to search result page.

Here is a link about how to add refiners to a search result page:

https://blogs.technet.microsoft.com/tothesharepoint/2013/11/10/how-to-add-refiners-to-your-search-results-page-in-sharepoint-2013/

Best Regards,

CY


TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


Doesn't work, this is the first thing we tried to do. When I tried this I got this error message:

"The settings could not be saved because of an internal error. The requested operation was not allowed. This managed property was configured to disallow changes to the requested property setting."

I did Google this error and found one other person that had the issue, however this is to do with the SocialTag managed property which has no crawled properties. DetectedLanguage does.

My guess here is that there is something about the internal workings of the ows_q_TEXT_TranslationLanguage crawled property which means Microsoft don't want it to be refinable. I say this because, as stated above, a custom managed property mapping onto that crawled property has no data.

fingerer on Sat, 20 Aug 2016 13:18:59


maybe you can set it using Powershell, I haven't try

see this

https://srevathi.wordpress.com/2013/06/29/powershell-to-make-managed-properties-sortable-and-refinable-in-sharepoint-2013/

somtimes operation in UI is not woring

Heley on Thu, 25 Aug 2016 08:38:10


maybe you can set it using Powershell, I haven't try

see this

https://srevathi.wordpress.com/2013/06/29/powershell-to-make-managed-properties-sortable-and-refinable-in-sharepoint-2013/

somtimes operation in UI is not woring


In my experience, items turned off in the UI are turned off for a good reason. Whilst making things sortable and refinable via PowerShell may be possible, I'm not going to risk a production system's stability. So this is really a question for Microsoft, are these things turned off for a good reason?