# No cached mapping for this field!

**URL:** https://discuss.elastic.co/t/no-cached-mapping-for-this-field/235810
**Category:** APM
**Created:** [June 4, 2020, 4:21pm UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/235810 "2020-06-04T16:21:11Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)
#### Post date: [June 12, 2020, 1:24pm UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/235810/2 "2020-06-12T13:24:08Z")

</div>

Hi @Alexandros888,  
the template that you are changing `apm-7.7.0-transaction` only contains the `settings`, the `mappings` are actually set in the `apm-7.7.0` template and shared for all apm indices. All the apm templates are versioned, which means that any manually applied changes via Kibana will only be valid for the current version. Therefore I'd generally advise to use configuration options in the `apm-server.yml` when available. Please see my answer to a similar question in another discuss post on [how to customize the template via APM Server](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-refresh-field-list-from-the-lanagement/236835/2).

---

_[View the full topic](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/235810)._