# No cached mapping for this field.Refresh field list from the lanagement

**URL:** https://discuss.elastic.co/t/no-cached-mapping-for-this-field-refresh-field-list-from-the-lanagement/236835
**Category:** APM
**Created:** [June 12, 2020, 6:49am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-refresh-field-list-from-the-lanagement/236835 "2020-06-12T06:49:21Z")
**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, 8:24am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-refresh-field-list-from-the-lanagement/236835/2 "2020-06-12T08:24:56Z")

</div>

Hi @wajika,  
instead of directly changing the `fields.yml` you can add additional fields to your mapping via configuring [`setup.template.append_fields`](https://www.elastic.co/guide/en/apm/server/current/configuration-template.html) in the `apm-server.yml`. If you want to enable `dynamic` for `http.request.headers` you could configure:

```auto
setup.template.append_fields:
- name: http.request.headers
  type: group
  dynamic: true

```

Be aware though that a template only gets applied to newly created indices. If the index existed before you changed the template, the changes won't be applied to this index. You can check if the template mapping has been applied by calling `GET apm-*transaction/_mapping`.

---

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