A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More


Feb 12, 2014
  5164
(2 votes)

Multi Search with EPiServer Find 7.5

With the release of EPiServer 7.5 we of course also released a 7.5 version of EPiServer Find. This release includes among other things a new feature to be able to handle multiple searches in one request. It will then return an IEnumerable<SearchResults<T>>. There are several use cases for this, several queries for a specific page can now be done in one round trip. Here you see a simple example of how to do it with the api.

results = service.MultiSearch<Article>()
                .Search<Article>(x => x.For("Banana").InField(y => y.Title))
                .Search<Article>(x => x.For("Annanas").InField(y => y.Title))
                .GetResult();

In the example above both queries search in the Article type and also returns the article type. It is also possible to search in different types and return a different type. Using the projections that are very powerful in EPiServer Find.

IEnumerable<SearchResults<string>> results = service.MultiSearch<string>()
    .Search<Article, string>(x => x.For(indexedArticle.Title).InField(y => y.Title).Select(y => y.Title))
    .Search<User, string>(x => x.For(indexedUser.Name).InField(y => y.Name).Select(y => y.Name)).GetResult();

The results are always returned in the same way as they are searched for. So the first result will be the first query. Also these will of course only count as one query against the index and will hopefully save you from any problems with too many requests.

Happy Finding!

Feb 12, 2014

Comments

Petter Klang
Petter Klang Feb 12, 2014 05:05 PM

Been looking forward to this!

Good job keep it up!

Petter Klang
Petter Klang Feb 12, 2014 05:05 PM

(double post)

Feb 12, 2014 06:37 PM

Very nice! So where is this documented? I'm particularily interested in the MultiUnifiedSearch functionality.

Mar 29, 2014 10:03 AM

Just to let you know: Multi Search fails if you use Take()/Skip() in your queries

Please login to comment.
Latest blogs
Looking back at Optimizely in 2025

Explore Optimizely's architectural shift in 2025, which removed coordination cost through a unified execution loop. Learn how agentic Opal AI and...

Andy Blyth | Dec 17, 2025 |

Cleaning Up Content Graph Webhooks in PaaS CMS: Scheduled Job

The Problem Bit of a niche issue, but we are building a headless solution where the presentation layer is hosted on Netlify, when in a regular...

Minesh Shah (Netcel) | Dec 17, 2025

A day in the life of an Optimizely OMVP - OptiGraphExtensions v2.0: Enhanced Search Control with Language Support and Synonym Slots

Supercharge your Optimizely Graph search experience with powerful new features for multilingual sites and fine-grained search tuning. As search...

Graham Carr | Dec 16, 2025

A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025