Take the community feedback survey now.

Jonas Bergqvist
Dec 8, 2016
  14443
(7 votes)

Exceptions in Find

Episerver Find can be used in many places on a site, like menus, navigations, listings, and searches. One thing that usually are forgotten when using Find is that it’s a service in the “cloud”, where you should handle possible exceptions.

EPiServer.Find.ServiceException

The “ServiceException” is the most important exception that should be handled in every place where Find is used. This exception will be thrown if the service is down, or if there is any other communication problem.

This exception inherits from ApplicationException.

EPiServer.Find.ClientException

The “ClientException” can be thrown when the query contains errors that is found at runtime. There is also several specific exceptions that inherit from “ClientException”.

This exception inherits from ApplicationException.

EPiServer.Find.SelfReferencingLoopException

The “SelfReferencingLoopException” will be thrown if a circular reference is found at runtime. There can for example exist a “Parent” property on a class, where the class of the parent property has a reference to the current class.

This exception inherits from ClientException.

EPiServer.Find.ProjectionException

The “ProjectionException” will be thrown if the projection (Select) is used in the wrong way in the query.

This exception inherits from ClientException.

EPiServer.Find.Api.InvalidIndexIdException

The “InvalidIndexIdException” will be thrown if the id of the index is null, or over 100 characters.

This exception inherits from ClientException.

EPiServer.Find.Api.InvalidDocumentIdException

The “InvalidDocumentIdException” will be thrown if the id of the document is null, or over 100 characters.

This exception inherits from ClientException.

EPiServer.Find.Api.InvalidSearchRequestException

The “InvalidSearchRequestException” will be thrown if the terms facet has been set to a value less than 0, or higher than 1000.

This exception inherits from ClientException.

Conclusion

Handle “EPiServer.Find.ServiceException” and “EPiServer.Find.ClientException” on all places where a query is created and executed against Find.

Dec 08, 2016

Comments

Please login to comment.
Latest blogs
Optimizely Web Experimentation on Single Page Applications

  Introduction Most of the modern web applications are built as Single Page applications (SPA) which provides a quick and smooth experience to the...

Ratish | Nov 16, 2025 |

Optimizely CMS - Learning by Doing: EP07 - Create Controller/View for Pages

  Episode 7  is Live!! The latest installment of my  Learning by Doing: Build Series  on  Optimizely CMS 12  is now available on YouTube! This vide...

Ratish | Nov 16, 2025 |

Multiple Languages in Optimizely CMS

I was exploring multi-languages in Optimizely CMS 12 – able to figure it out quickly in a few steps. Let’s get started. 1. Enable Languages... The...

Madhu | Nov 15, 2025 |

Optimizely CMS RSS Feed Integration Library — Version 2 Release

Optimizely CMS Easy RSS Feed Integration Library — Now in v2 A while ago I launched a NuGet-package called DavidHome.RssFeed to make RSS feed...

David Drouin-Prince | Nov 15, 2025 |

Full implementation - Fallback languages with Optimizely Graph

Nowadays, many people choose a headless approach when developing Optimizely CMS/Commerce projects using Opti Graph. One challenge we may face is...

Binh Nguyen Thi | Nov 15, 2025

Optimizely Connect Platform (OCP): Extending the Optimizely One Ecosystem

Discover how Optimizely Connect Platform (OCP) enables seamless integrations across the Optimizely One ecosystem. Learn about app models, sync type...

Andrew Markham | Nov 14, 2025 |