# Fix mapping conflict
**URL:** https://discuss.elastic.co/t/fix-mapping-conflict/114309
**Category:** Kibana
**Created:** [January 5, 2018, 4:32pm UTC](https://discuss.elastic.co/t/fix-mapping-conflict/114309 "2018-01-05T16:32:41Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Dmitry\_Reshetnik](https://discuss.elastic.co/u/Dmitry_Reshetnik)
#### Post date: [January 5, 2018, 4:32pm UTC](https://discuss.elastic.co/t/fix-mapping-conflict/114309/1 "2018-01-05T16:32:41Z")
I have a Kibana not owned by me.
As of now it contains 1000+ fields (generated from JSON inputs).
There are few fields which were (maybe manually configured as String), and few visualizations which used these fields.
At some moment the index fields list was refreshed, and these fields became Number. And for some time were indexed as numbers.
Now we have conflicts "The type of this field changes across indices. It is unavailable for many analysis functions."
Is there any chance to convert it to String without losing the data?
---
### Author:  [@dsnider](https://discuss.elastic.co/u/dsnider)
#### Post date: [January 5, 2018, 7:43pm UTC](https://discuss.elastic.co/t/fix-mapping-conflict/114309/2 "2018-01-05T19:43:46Z")
You will need to convert all the data in that specific field to a string. Once you do that you'd need to reindex that data in Kibana.
This article can you good starting point
> **[Changing Mapping with Zero Downtime
| Elastic](https://www.elastic.co/blog/changing-mapping-with-zero-downtime)**
>
> Update November 2, 2015: Make sure to check out the updates with Elasticsearch mappings introduced in the 2.0 release.Update May 1, 2017: This blog was originally published several major versions...
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 2, 2018, 7:43pm UTC](https://discuss.elastic.co/t/fix-mapping-conflict/114309/3 "2018-02-02T19:43:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.