# No cached mapping for this field --\> APM

**URL:** https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196
**Category:** APM
**Created:** [October 5, 2018, 10:49am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196 "2018-10-05T10:49:45Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![roncohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roncohen/32/22881_2.png) [@roncohen](https://discuss.elastic.co/u/roncohen)
#### Post date: [October 12, 2018, 6:24pm UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196/4 "2018-10-12T18:24:24Z")

</div>

> [@umapati](#):
>
> I have update the fields.yml located @ /etc/apm-server with the missing parameters. However, I dont see them updated under kibana.

Thanks! The recommended way to get additional fields indexed at the moment is to add them to "tags": [Agent API | APM Node.js Agent Reference [4.x] | Elastic](https://www.elastic.co/guide/en/apm/agent/nodejs/current/agent-api.html#apm-set-tag)

For some fields that might be impossible or very inconvenient. It turns out that unfortunately 6.4 introduced a small bug which requires that you set `setup.template.fields` to `fields.yml` in order for apm-server to load the file. I've filed an issue [fields.yml is ignored but still shipped with packages · Issue #8607 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/8607).

Please also make sure you've set `setup.template.overwrite: true` and that it only works for newly created indices.

Let me know if that helps.

/Ron

---

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