# Ingest pipeline (attachment) unable to find base64 encoded field

**URL:** <https://discuss.elastic.co/t/ingest-pipeline-attachment-unable-to-find-base64-encoded-field/371140>\
**Category:** Elasticsearch\
**Tags:** ingest-pipeline\
**Created:** [November 27, 2024, 1:44pm UTC](https://discuss.elastic.co/t/ingest-pipeline-attachment-unable-to-find-base64-encoded-field/371140 "2024-11-27T13:44:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![petlit2049](https://avatars.discourse-cdn.com/v4/letter/p/e5b9ba/32.png) [@petlit2049](https://discuss.elastic.co/u/petlit2049)\
**Post date:** [November 27, 2024, 1:44pm UTC](https://discuss.elastic.co/t/ingest-pipeline-attachment-unable-to-find-base64-encoded-field/371140/1 "2024-11-27T13:44:24Z")

</div>

Hi!

I have a very basic ingest pipeline case where I'd like to call an attachment processor. A simple curl -X PUT with provided Json-data works perfectly but when I do the following from my c# code:

`var response = await _docDb.IndexAsync<Document>(doc, i => i.Index("document").Pipeline("attachment").Id(doc.Id));`

I get a:

`field [ContentBase64Encoded] not present as part of path [ContentBase64Encoded]`

The POCO is super simple with three public string properties:

```auto
public string? Id

public string? FileName

public string? ContentBase64Encoded

```

It seems like the attachment processor is unable to find my POCO property using the `"field": "ContentBase64Encoded"` specification.

What am I doing wrong here. I'm running v8.16 of Elasticsearch and the latest .Net sdk.

Many thanks!