Hi Henrik,

No there will be no examples of this. The general idea is that it just works ;)

Example code: 

var client = Client.CreateFromConfig();
            var testObject = new TestObject() {ord = "cykelstyre"};

            client.Index(testObject);

            Console.ReadKey();

            var result = client.Search<TestObject>(Language.Swedish).For("cykel").InField(x => x.ord).GetResult();
            Console.WriteLine("RESULTS: ");
            foreach (var searchResult in result)
            {
                Console.WriteLine("Result " +searchResult.ord );
            }
            Console.ReadKey();

I tried this now with the exakt word you are using and it didn't work for me, I added it to both one custom object and one standard page where I search with unified search.

Ok, I tried now to build a simple example and saw that my problem was that I did not defined field like you do.

If I use .InField ... it works, but if I does not define it or use InAllField it does not work.

Do you know if that is how it should work, or should it work using InAllFields?

I do know that it shouldn't work when searching in the all field. Stemming doesn't work at all in the all field.

See this for more info: http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Find/8/DotNET-Client-API/Searching/Languages/

/Marcus

Ok, then I understand, that was what I was afraid of.
I have to redifine my searches to make them more effective

Is compound word splitting working in UnifiedSearch too? If I search for "hem" I do not get pages comtaining only the words "familjehem" or "hemtjänst".

There is currently a problem with short words during compound splitting due to a performance optimization that can make the splitting heuristics too relaxed.

We have a new version of the splitter implemented that should be much better but it will be available in a later version.

/ John Johansson, Backend Developer, Hosted Services