Henrik Fransas
Mar 18, 2016
visibility 5087
star star star star star
(3 votes)

Using AppSettings instead of ConfigSections for Episerver Find

In the documentation for Episerver Find it says that you should write like this in your app.config or web.config file:

<configuration>
     <configSections>
            <section
            name="episerver.find"
            type="EPiServer.Find.Configuration, EPiServer.Find" requirePermission="false"/>
        </configSections>
        <episerver.find
            serviceUrl="http://..."
        defaultIndex="myindex"/>
</configuration>

There also exist another way to set this up that are a little hidden, and that are to go through the appsettings in the config file. So instead of writing like the above you can write like this:

<appSettings>
    <add key="episerver:FindServiceUrl" value="http://..." />
    <add key="episerver:FindDefaultIndex" value="myindex" />
  </appSettings>
  

Depending on how you have set up you deployment pipeline this could be a nice way since it is easier to implement config transformation for this I think.

Mar 18, 2016

Comments

Vincent
Vincent Mar 22, 2016 04:40 AM

Good to know :)

For my current project, I remove the element first, then insert with different index key 


Henrik Fransas
Henrik Fransas Mar 22, 2016 07:57 AM

That is true!

Missed to inform about that. Thanks!

Jonas Carlbaum
Jonas Carlbaum Oct 22, 2018 08:57 AM

@episerver please update the documentation about *Staged deployments* settings in https://world.episerver.com/documentation/developer-guides/CMS/Deployment/deployment-scenarios/Deploying-to-Azure-webapps/#StagedDeployment to inform about how to enable a separate Find-index on Deployment slots.

error Please login to comment.
Latest blogs
Finding Thomas Part 3 - The Moment of Recognition

Remember Thomas? In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard...

Ritu Madan | Jun 26, 2026

Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026