# Default dynamic template uses enum for text fields instead of keyword
**URL:** https://discuss.elastic.co/t/default-dynamic-template-uses-enum-for-text-fields-instead-of-keyword/349821
**Category:** Elasticsearch
**Created:** [December 21, 2023, 6:57pm UTC](https://discuss.elastic.co/t/default-dynamic-template-uses-enum-for-text-fields-instead-of-keyword/349821 "2023-12-21T18:57:06Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Julia\_Dai](https://discuss.elastic.co/u/Julia_Dai)
#### Post date: [December 21, 2023, 6:57pm UTC](https://discuss.elastic.co/t/default-dynamic-template-uses-enum-for-text-fields-instead-of-keyword/349821/1 "2023-12-21T18:57:06Z")
We're using Elasticsearch dynamic mapping for our indexes, but for some reason our indexes are mapping text fields to enum sub fields instead of keyword sub fields like it says in the docs ([Dynamic field mapping | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.11/dynamic-field-mapping.html)).
When we use an emulator, we can correctly do term queries on text fields by appending ".keyword" to the field path, but in our production environments we have to append ".enum" instead.
Any idea why our default dynamic template seems to be incorrectly doing the index mapping? Where are default dynamic templates stored?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 18, 2024, 6:57pm UTC](https://discuss.elastic.co/t/default-dynamic-template-uses-enum-for-text-fields-instead-of-keyword/349821/2 "2024-01-18T18:57:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.