# Mapper\_parsing\_exception: object mapping tried to parse field as object, but found a concrete value

**URL:** <https://discuss.elastic.co/t/mapper-parsing-exception-object-mapping-tried-to-parse-field-as-object-but-found-a-concrete-value/227572>\
**Category:** Elasticsearch\
**Created:** [April 10, 2020, 11:39pm UTC](https://discuss.elastic.co/t/mapper-parsing-exception-object-mapping-tried-to-parse-field-as-object-but-found-a-concrete-value/227572 "2020-04-10T23:39:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nsanthosh](https://avatars.discourse-cdn.com/v4/letter/n/67e7ee/32.png) [@nsanthosh](https://discuss.elastic.co/u/nsanthosh)\
**Post date:** [April 10, 2020, 11:39pm UTC](https://discuss.elastic.co/t/mapper-parsing-exception-object-mapping-tried-to-parse-field-as-object-but-found-a-concrete-value/227572/1 "2020-04-10T23:39:19Z")

</div>

Could you suggest how to handle different value types mapped to a filed i.e. object and text?

I have an index that has a mapping as listed below. The same is started failing to accept the text value. I don't have control over upstream data. I have tried using the dynamic flag that didn't help.

```auto
"Id": {
    "dynamic": "true",
    "properties": {
      "$exists": {
        "type": "boolean"
      }
    }

```

Data format:  
version 1: `"Id": {"$exists": true}`  
version 2: `"Id": "user12345"`

---

<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:** [May 8, 2020, 11:39pm UTC](https://discuss.elastic.co/t/mapper-parsing-exception-object-mapping-tried-to-parse-field-as-object-but-found-a-concrete-value/227572/2 "2020-05-08T23:39:25Z")

</div>

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