# Field data type conflict

**URL:** https://discuss.elastic.co/t/field-data-type-conflict/327507
**Category:** Kibana
**Created:** [March 12, 2023, 5:30pm UTC](https://discuss.elastic.co/t/field-data-type-conflict/327507 "2023-03-12T17:30:19Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Sara\_YB](https://avatars.discourse-cdn.com/v4/letter/s/5f8ce5/32.png) [@Sara\_YB](https://discuss.elastic.co/u/Sara_YB)
#### Post date: [March 12, 2023, 5:30pm UTC](https://discuss.elastic.co/t/field-data-type-conflict/327507/1 "2023-03-12T17:30:19Z")

</div>

I have nested field type (text, long). After upgrading to v 8.6, a conflict happened in this field. Below is the message I got:  
"The type of the (field name) field changes across indices and might not be available for search, visualizations, and other analysis."  
How can I resolve this conflict issue without losing my data?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [March 19, 2023, 11:05pm UTC](https://discuss.elastic.co/t/field-data-type-conflict/327507/2 "2023-03-19T23:05:22Z")

</div>

It'd be helpful if you could share the mappings of the conflicting indices.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 16, 2023, 11:05pm UTC](https://discuss.elastic.co/t/field-data-type-conflict/327507/3 "2023-04-16T23:05:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.