# Property mapping elasticsearch

**URL:** <https://discuss.elastic.co/t/property-mapping-elasticsearch/283580>\
**Category:** Elasticsearch\
**Tags:** language-clients\
**Created:** [September 7, 2021, 8:41pm UTC](https://discuss.elastic.co/t/property-mapping-elasticsearch/283580 "2021-09-07T20:41:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stevejgordon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stevejgordon/32/80912_2.png) [@stevejgordon](https://discuss.elastic.co/u/stevejgordon)\
**Post date:** [September 8, 2021, 6:57am UTC](https://discuss.elastic.co/t/property-mapping-elasticsearch/283580/2 "2021-09-08T06:57:52Z")

</div>

You seem to have repeated pretty much the same question from your [earlier post](https://discuss.elastic.co/t/how-to-read-different-field-names-with-same-field-value-elasticsearch/283314/2). As answered there, the default configuration assumes that types are camel-case in JSON and the documentation I linked to provides guidance on changing that behaviour. You can also look at [Fluent mapping](https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/fluent-mapping.html) for configuring the JSON name for properties which potentially could meet your dynamic requirement to set that when the application starts up for example.

---

_[View the full topic](https://discuss.elastic.co/t/property-mapping-elasticsearch/283580)._