# Field type (Mapping) conflicts

**URL:** https://discuss.elastic.co/t/field-type-mapping-conflicts/311967
**Category:** Kibana
**Created:** [August 11, 2022, 10:13pm UTC](https://discuss.elastic.co/t/field-type-mapping-conflicts/311967 "2022-08-11T22:13:16Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![JLeysens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jleysens/32/67404_2.png) [@JLeysens](https://discuss.elastic.co/u/JLeysens)
#### Post date: [August 12, 2022, 8:53am UTC](https://discuss.elastic.co/t/field-type-mapping-conflicts/311967/2 "2022-08-12T08:53:05Z")

</div>

Hello @ELKcgnuser !

You will need to reindex some set of the indices being targetted by the data view (legacy: index pattern) that you are using. To convert types you could use an ingest pipeline, for example:

> **[Reindex API | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#reindex-with-an-ingest-pipeline)**

See related discuss issue:

> [@Kibana conflict type field](https://discuss.elastic.co/t/kibana-conflict-type-field/270667):
>
> How i can resolve this issues. Kibana field type conflict

---

_[View the full topic](https://discuss.elastic.co/t/field-type-mapping-conflicts/311967)._