COVEO_LINQ_TO_COVEO_INDEX_EXCEPTION InvalidCustomField - After upgrading from build 1226 to 1266
I have a rather big issue, that I hope you can help me resolve. I've recently been tasked with upgrading Coveo from 1084 to 1266. This has gone quite well, and I've reached 1266 yesterday. Sadly though, it seems my search index is now broken.
I believe I've updated my configuration correctly, here is a snippet:
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <coveo> <defaultIndexConfiguration type="Coveo.Framework.Configuration.CoveoIndexConfiguration, Coveo.Framework"> <fieldMap type="Coveo.SearchProvider.CoveoFieldMap, Coveo.SearchProvider"> <param desc="coveoReflectionFactory" type="Coveo.Framework.Utils.CoveoReflectionFactory, Coveo.Framework" /> <fieldNames hint="raw:AddFieldByFieldName"> <fieldType fieldName="Description" settingType="Coveo.Framework.Configuration.FieldConfiguration, Coveo.Framework" isFacet="true" isSortable="true" includeForFreeTextSearch="true" /> </fieldNames> </fieldMap> </defaultIndexConfiguration> </coveo> </sitecore> </configuration>
I get the following exception:
I've tried a full reindex, both from Sitecore and Admin interface. But that didn't change anything.
Do anyone have any idea what might be wrong?
The version you upgraded for changed the way fields are selected in a new pipeline (as seen in the documentation)
Since the field is correctly configured, what probably happens here is that the field you are trying to fetch is called "Description", and is excluded by the ExcludeFieldsFromConfigProcessor in the coveoIndexingGetFields pipeline since the Description field is excluded by default from the configuration.
To validate this theory, you can either try to comment out the ExcludeFieldsFromConfigProcessor or remove the "
Meanwhile, we will look at this issue on our side.