# IndexFields

The fields to store as Index fields in IDOL server. IDOL Server treats these fields as Index fields for the documents that you send in the index action.

NOTE: Micro Focus recommends that you use field configuration to set Index fields, instead of setting this parameter for a single index action.

You must only store fields that contain text that you frequently query conceptually as Index fields.

Index fields are processed linguistically when they are stored in IDOL server. IDOL server applies stemming and stop lists to text in Index fields before they are stored, which allows IDOL server to process queries for these fields more quickly (typically `DRETITLE` and `DRECONTENT` are fields that must be set up as Index fields).

Do not store URLs or content that you are unlikely to use in Index fields. Also, Micro Focus recommends you do not store fields as Index fields that are queried frequently but whose value is only ever queried in its entirety. Indexing all fields in documents might slow down the indexing process, increase disk usage and requirements.

Separate multiple fields with commas. There must be no space before or after a comma. You can use wildcards.

When identifying fields use the formats:

- `/FieldName` to match root-level fields

- `*/FieldName` to match all fields except root-level

- `/Path/FieldName` to match fields that the specified path points to.

If you specify only the field name, IDOL Server automatically adds a `*/` to it.

Actions: | DREADD DREADDDATA
Type: | String
Default: |
Example: | `IndexFields=*/DRECONTENT,*/DRETITLE` In this example, `DRECONTENT` and `DRETITLE` fields are stored as Index fields in IDOL Server
See Also: | Index configuration parameter

_FT_HTML5_bannerTitle.htm