# Mapper\_parsing\_exception,reason:object mapping for \[process\] tried to parse field \[process\] as object, but found a concrete value

**URL:** <https://discuss.elastic.co/t/mapper-parsing-exception-reason-object-mapping-for-process-tried-to-parse-field-process-as-object-but-found-a-concrete-value/330979>\
**Category:** Elasticsearch\
**Tags:** docker, runtime-fields\
**Created:** [April 27, 2023, 4:35pm UTC](https://discuss.elastic.co/t/mapper-parsing-exception-reason-object-mapping-for-process-tried-to-parse-field-process-as-object-but-found-a-concrete-value/330979 "2023-04-27T16:35:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [April 27, 2023, 5:39pm UTC](https://discuss.elastic.co/t/mapper-parsing-exception-reason-object-mapping-for-process-tried-to-parse-field-process-as-object-but-found-a-concrete-value/330979/2 "2023-04-27T17:39:44Z")

</div>

Couple of Things...

looks like you are using a default mapping instead of creating a template which is not best practice for production.

Good that you understand the issue that you can not have a mapping that supports both an object and a concrete field.

In general, to fix this you will need to create an ingest pipeline that will look at the data and put that concrete field into one of the object fields...

Think I showed a way to do that [here](https://discuss.elastic.co/t/field-with-different-types-on-same-index/315047/5)

---

_[View the full topic](https://discuss.elastic.co/t/mapper-parsing-exception-reason-object-mapping-for-process-tried-to-parse-field-process-as-object-but-found-a-concrete-value/330979)._