# Providing document\_id in function beat for decode\_json\_fields results in effectively no updates to any records **URL:** \ **Category:** Beats\ **Tags:** functionbeat\ **Created:** [February 5, 2021, 4:15pm UTC](https://discuss.elastic.co/t/providing-document-id-in-function-beat-for-decode-json-fields-results-in-effectively-no-updates-to-any-records/263434 "2021-02-05T16:15:33Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![ryantomaselli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryantomaselli/32/83397_2.png) [@ryantomaselli](https://discuss.elastic.co/u/ryantomaselli)\ **Post date:** [February 6, 2021, 10:00pm UTC](https://discuss.elastic.co/t/providing-document-id-in-function-beat-for-decode-json-fields-results-in-effectively-no-updates-to-any-records/263434/3 "2021-02-06T22:00:41Z")
> [@Functionbeat does not update documents with existing \_id](https://discuss.elastic.co/t/functionbeat-does-not-update-documents-with-existing-id/252901): > > Hello, I am currently deploying Functionbeat configured to accept events from an SQS queue. The goal is to use a processor/ingest pipeline to extract and set \_id from fields in the incoming messages. Documents with existing \_id do not appear to be pushed from functionbeat at all. I have attempted to isolate the behavior with the below steps: Write message to aws sqs queue i.e. aws sqs send-message --queue-url \ --message-body '{ "val": "foo", }' --message-group-id f1 --message-de… Hmmm looking like this is either a bug or just not supported. Seems like it should be a feature. What's the point of being able specify the id if it means the record can never recieve updates. --- _[View the full topic](https://discuss.elastic.co/t/providing-document-id-in-function-beat-for-decode-json-fields-results-in-effectively-no-updates-to-any-records/263434)._