# Can a field like "name.last" be the target field of "enrich" in the ingest pipeline gui?

**URL:** <https://discuss.elastic.co/t/can-a-field-like-name-last-be-the-target-field-of-enrich-in-the-ingest-pipeline-gui/296418>\
**Category:** Elasticsearch\
**Tags:** ingest-pipeline\
**Created:** [February 7, 2022, 6:10am UTC](https://discuss.elastic.co/t/can-a-field-like-name-last-be-the-target-field-of-enrich-in-the-ingest-pipeline-gui/296418 "2022-02-07T06:10:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aloha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aloha/32/101434_2.png) [@Aloha](https://discuss.elastic.co/u/Aloha)\
**Post date:** [February 7, 2022, 6:10am UTC](https://discuss.elastic.co/t/can-a-field-like-name-last-be-the-target-field-of-enrich-in-the-ingest-pipeline-gui/296418/1 "2022-02-07T06:10:18Z")

</div>

Trying to setup an ingest pipeline via the gui after setting up an enrich policy similar to [this example](https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-match-enrich-policy-type.html).

The target field is `name.last` and testing the pipeline with documents via the GUI works fine but trying to ingest the same values throws a parsing error and it can't access the `name.last` field. Are accessing fields such as `name.last` supported?

---

<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:** [February 7, 2022, 6:30am UTC](https://discuss.elastic.co/t/can-a-field-like-name-last-be-the-target-field-of-enrich-in-the-ingest-pipeline-gui/296418/2 "2022-02-07T06:30:07Z")

</div>

Can you post your enrich code ... the enrich Index, your enrich processor, and a sample doc ... that will help.

In short if you are enriching a multiple fields **all** those fields will be sub fields of your target field... so if your `name.last` is already defined in your mapping as a concrete field like a `keyword` you will get an error as the enrich will try to treat `name.last` as an object with subfields... if you want to them put them in a bunch of specific fields you would use other processors afterwards like the `set` processor.. hope that makes sense... show us what you are doing and we can help.

Perhaps this example will make more sense.

> **[Example: Enrich your data based on exact values | Elasticsearch Guide \[7.17\]...](https://www.elastic.co/guide/en/elasticsearch/reference/current/match-enrich-policy-type.html)**

---

<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:** [March 7, 2022, 6:30am UTC](https://discuss.elastic.co/t/can-a-field-like-name-last-be-the-target-field-of-enrich-in-the-ingest-pipeline-gui/296418/3 "2022-03-07T06:30:41Z")

</div>

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