# Filebeats creating the incorrect datatype in index

**URL:** https://discuss.elastic.co/t/filebeats-creating-the-incorrect-datatype-in-index/196849
**Category:** Beats
**Tags:** filebeat
**Created:** [August 26, 2019, 11:13pm UTC](https://discuss.elastic.co/t/filebeats-creating-the-incorrect-datatype-in-index/196849 "2019-08-26T23:13:13Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![mbradsher](https://avatars.discourse-cdn.com/v4/letter/m/c2a13f/32.png) [@mbradsher](https://discuss.elastic.co/u/mbradsher)
#### Post date: [September 5, 2019, 5:40pm UTC](https://discuss.elastic.co/t/filebeats-creating-the-incorrect-datatype-in-index/196849/5 "2019-09-05T17:40:07Z")

</div>

Thank you for your help. The real value of var3 is 'stepid' and the issue only happens intermittently so I do not expect this is from a name collision. Instead I took your suggestion to be explicit about the mapping by using the experimental [setup.template.append\_fields](https://www.elastic.co/guide/en/beats/filebeat/7.3/configuration-template.html) property.

I've run into new problems but they are expressed on a new forum [here.](https://discuss.elastic.co/t/does-setup-template-append-fields-work-for-multifields/198125)

---

_[View the full topic](https://discuss.elastic.co/t/filebeats-creating-the-incorrect-datatype-in-index/196849)._