--- title: Update your configuration to the Coveo for Sitecore 5 initial release slug: lbnf0387 canonical_url: https://docs.coveo.com/en/lbnf0387/ collection: coveo-for-sitecore-v5 source_format: adoc --- # Update your configuration to the Coveo for Sitecore 5 initial release When upgrading from Coveo for Sitecore 4.1 to Coveo for Sitecore 5, you need to make several changes in your Sitecore instance configuration files. > **Important** > > The instructions below pertain to upgrade scenarios 2 and 3 in the [Coveo for Sitecore 4 to Coveo for Sitecore 5 upgrade procedure](https://docs.coveo.com/en/2642#identify-your-upgrade-scenario) article and assume that you have performed all prior steps in your upgrade scenario. ## Manually update the Coveo configuration files The Coveo configuration files are located in the `\App_Config\Include\Coveo` and `\App_Config\Modules\Coveo` folders. When upgrading, you must compare the changes to the `.example` files from your current Coveo for Sitecore version with the ones in the build you're upgrading to. Then, you can merge these changes into your current configuration files. This method lets you keep your own customization intact, while still benefiting from the latest enhancements brought in the product. You can use a merge tool such as [WinMerge](http://winmerge.org/) to accomplish this. As a result of the feature changes between the October 2018 release of Coveo for Sitecore 4.1 and the November 2018 release of Coveo for Sitecore 5, here are the modifications you must make in the configuration files: ### In the `Coveo.SearchProvider.config` file . The lines below, associated with the `AddCoveoFieldsProcessor`, have been removed. This processor is no longer required. You may delete these lines in your configuration. ```xml ``` . All of the following lines must be removed from the `Coveo.SearchProvider.config` file, as they were only valid for on-premises instances of Coveo for Sitecore. ```xml ``` ```xml ``` ```xml http://localhost/AdminService C:\CES7\ default ADMIN 52800 CMF ADMIN 52810 HTTPS ``` ```xml C:\CES7\Config\Certificates\cert-iis.p12 https://localhost:52810/7.0/CoveoSearchService amqp://localhost:5682/ guest false ``` ```xml ``` ```xml master;web ``` ```xml true ``` . If your `\App_Config\Include\Coveo` folder contains the `Coveo.SearchProvider.Fields.Custom.config` file, this means Coveo has already recovered the fields that used to be indexed through the `AddTemplateFieldsProcessor` and they're now included through the `IncludeFieldsFromConfigOnlyProcessor`. The `AddTemplateFieldsProcessor` is therefore no longer required. In turn, the `AddTemplateFieldsProcessor` invokes the `coveoIndexingGetTemplates` pipeline. Since the `coveoIndexingGetTemplates` pipeline will no longer be invoked, it too is no longer required. You can therefore remove all of the lines below from your configuration. ```xml ``` ```xml true ``` > **Note** > > If your `App_Config\Include\Coveo` folder does _not_ contain the `Coveo.SearchProvider.Fields.Custom.config` file, steps will be provided further in the upgrade steps to move away from the traditional inclusion of fields through configuration file settings to the new and simpler method using the **Command Center** user interface. . The following lines, associated with previously `sys`-prefixed fields, have been edited and moved from the `` element to the `` element. Apply these changes in your configuration. ```xml ``` Additionally, if you've created and are using custom result template `.cshtml` files, remove all `sys` prefixes from the field names in those files to ensure that the new field names are referenced, as per the `fieldName` attribute values above. On the other hand, the `default.cshtml` result template file should be automatically modified during the upgrade and should therefore not require any modifications on your part. . The `ref` attribute value of the `` element has been changed. The element now reads as follows: ```xml ``` Apply this modification in your configuration. . The following block has been removed in relation to the end of support for LINQ queries. ```xml ``` . In the September 2018 release of Coveo for Sitecore 4.1, the element below appeared as an optional addition in the `` element: ```xml ``` Coveo now strongly recommends that you add this `` element which reverses the default field hashing behavior. Since Coveo for Sitecore now addresses situations where two fields have identical names but different types and field collisions rarely occur, hashing field names should only be used as a last resort (see the `isSourceSpecific` parameter in [About the Coveo Search Provider configuration file](https://docs.coveo.com/en/2562#fieldnames)). . To fix an issue with FieldReaderCache, locate the `defaultIndexConfiguration/fieldReaders` element. Within this node, add the following line: ```xml coveoFieldReaderMap ``` ### In the `Coveo.SearchProvider.Custom.config` file Remove the following block. ```xml ``` ### In the `Coveo.SearchProvider.Rest.config` file . Locate the following block which is associated with on-premises instances of Coveo for Sitecore. ```xml replace this with your own application secret ``` Replace this block with the line below. ```xml ``` . Locate the following line which is also associated with on-premises instances of Coveo for Sitecore. ```xml http://localhost:8080 ``` Replace this line with the one below. ```xml https://platform.cloud.coveo.com ``` . The following code block has been removed. Apply this modification to your configuration. ```xml ``` . The following code block has been removed. Apply this modification to your configuration. ```xml ``` ### In the `Coveo.UI.Controls.config` file . The elements below have been removed, along with all their children, as a result of the end of support for the Legacy Search UI Framework. Apply these modifications to your configuration. ** `` ** `` ** `` ** `` ** `` ** `` . Locate the following code block. ```xml ``` Replace this block with the following. ```xml ```