# Mapping conflict but no way to resolve anymore
**URL:** https://discuss.elastic.co/t/mapping-conflict-but-no-way-to-resolve-anymore/292617
**Category:** Kibana
**Created:** [December 21, 2021, 10:13pm UTC](https://discuss.elastic.co/t/mapping-conflict-but-no-way-to-resolve-anymore/292617 "2021-12-21T22:13:36Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@seanziee](https://discuss.elastic.co/u/seanziee)
#### Post date: [December 21, 2021, 10:13pm UTC](https://discuss.elastic.co/t/mapping-conflict-but-no-way-to-resolve-anymore/292617/1 "2021-12-21T22:13:36Z")
In the past, you could click on the conflict field and see which indices are causing the conflict but for some reason you have removed that functionality. Is there some way to see which index is causing the conflict?
---
### Author:  [@dosant](https://discuss.elastic.co/u/dosant)
#### Post date: [December 22, 2021, 10:56am UTC](https://discuss.elastic.co/t/mapping-conflict-but-no-way-to-resolve-anymore/292617/2 "2021-12-22T10:56:01Z")
Hi, this will be fixed soon
>
>
> \*\*Kibana version:\*\* 7.15.0
>
> \*\*Elasticsearch version:\*\* 7.15.0
>
> \*\*Describe th…e bug:\*\*
> This was requested back in: https://github.com/elastic/kibana/issues/45135
> It looks like it was implemented as it was working on 7.12.1:
>
> \
>
> And now looking at 7.15 we see that conflicting indices are no longer showing up:
>
> \
>
>
> \*\*Expected behavior:\*\*
> Clicking on field should show conflicting indices.
There is a workaround: [[Index Patterns] Conflicting fields no longer show matching indices · Issue #114361 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/114361#issuecomment-968750731)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 19, 2022, 10:56am UTC](https://discuss.elastic.co/t/mapping-conflict-but-no-way-to-resolve-anymore/292617/3 "2022-01-19T10:56:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.