# Type of a Field

**URL:** <https://discuss.elastic.co/t/type-of-a-field/379238>\
**Category:** Kibana\
**Tags:** data-views\
**Created:** [June 17, 2025, 10:44am UTC](https://discuss.elastic.co/t/type-of-a-field/379238 "2025-06-17T10:44:45Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [June 18, 2025, 10:22am UTC](https://discuss.elastic.co/t/type-of-a-field/379238/4 "2025-06-18T10:22:22Z")

</div>

Suggest to read:

> **[ignore\_malformed | Reference](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/ignore-malformed)**
>
> Sometimes you don’t have much control over the data that you receive. One user may send a login field that is a date, and another sends a login field...

and

> [@Ignore\_malformed within an object](https://discuss.elastic.co/t/ignore-malformed-within-an-object/363147):
>
> Hi, can anyone provide confirmation or clarification if using ignore\_malformed on a property within an object is supported. The docs say they are not supported on object types but does this extend to properties within the object? for example : "dynamic\_templates": [ { "custom\_date\_iso": { "path\_match": "custom.\*", "match\_mapping\_type": "date", "mapping": { "format": "strict\_date\_optional\_time", "ignore\_malformed…

In your specific case, the type "object" is explicitly excluded from the use of ignore\_malformed, which would be a common approach in these cases.

I guess you _could_ try to use ingest pipelines to tidy up any bad input data ... often better to try to "fix" this sort of issue at source (excuse the pun).

---

_[View the full topic](https://discuss.elastic.co/t/type-of-a-field/379238)._