# Not able to create multiple nested type mapping for hierarchical json data

**URL:** <https://discuss.elastic.co/t/not-able-to-create-multiple-nested-type-mapping-for-hierarchical-json-data/209803>\
**Category:** Elasticsearch\
**Created:** [November 28, 2019, 7:18am UTC](https://discuss.elastic.co/t/not-able-to-create-multiple-nested-type-mapping-for-hierarchical-json-data/209803 "2019-11-28T07:18:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [November 28, 2019, 8:08am UTC](https://discuss.elastic.co/t/not-able-to-create-multiple-nested-type-mapping-for-hierarchical-json-data/209803/2 "2019-11-28T08:08:36Z")

</div>

You don’t use the dot notation in the mappings- ‘elementType’ is declared as type nested then you have a ‘properties’ field at the same level to declare the fields it holds eg “entity”.  
Before you do - are you sure you need the overhead of nested docs? If the objects only have one property (“name”) there’s no need for a nested doc. See this [flowchart](https://discuss.elastic.co/t/indexing-hierarchical-couchbase-documents/70400/2)

---

_[View the full topic](https://discuss.elastic.co/t/not-able-to-create-multiple-nested-type-mapping-for-hierarchical-json-data/209803)._