Developer forum

Hi Barend,

This issue has been fixed internally and is awaiting release. Because the fix is part of a feature release, it will take a month or two to be in R1.

In the meantime, there are a couple of workarounds you can use to solve the issue.

• Change the index definition file on disk to remove the field configuration
  All index files reside in /Files/System/Repositories/[YourRepository]/[YourIndex].index
• Remove the schema extender field from the index and add it back again after

With regard to the naming. It's called Excluded fields on purpose because that's what it does. By default, the schema extender includes all product fields in the system in the index. This is to make sure that if you add a new custom or category field, it's available in the index. However, there may be situations where certain fields should be excluded for one reason or another. Those are the ones you select in the Excluded fields list. So, the schema extender includes all fields by default, except the ones selected under Excluded fields.

If you only want the index to include the fields you select manually, then you shouldn't use the schema extender at all. Simply create the fields you want. With the release that I mentioned in the beginning, this gets a lot easier as it's possible to create actual index fields from the definition in a schema extender without having to add the schema extender itself. Currently, you would have to configure the field manually.

- Jeppe