# Mapping issue
**URL:** https://discuss.elastic.co/t/mapping-issue/347532
**Category:** Elasticsearch
**Tags:** painless
**Created:** [November 20, 2023, 1:16pm UTC](https://discuss.elastic.co/t/mapping-issue/347532 "2023-11-20T13:16:06Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@VirusProtect](https://discuss.elastic.co/u/VirusProtect)
#### Post date: [November 20, 2023, 1:16pm UTC](https://discuss.elastic.co/t/mapping-issue/347532/1 "2023-11-20T13:16:06Z")
Hi, I'm working with fields `changes.to` and `changes.from` in Elasticsearch. These fields sometimes hold simple strings, and other times, they are objects with various values like address, name, etc.
I'm facing an error: "failed to parse field `[changes.from]` of type `[text]` ". This happens when the field is mapped as `text` . However, if I map it as an `object` , I encounter problems when `changes.to` and `changes.from` contain just a simple keyword.
Can anyone suggest a solution for handling these fields ? Maybe we can write some painless script ? Or what would be the best solution ?
---
### Author:  [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [November 21, 2023, 5:37pm UTC](https://discuss.elastic.co/t/mapping-issue/347532/2 "2023-11-21T17:37:33Z")
Hi @VirusProtect,
What do you mean by handle the fields? To confirm, for the object case is it a single level object or nested:
{ name: 'Bruce', surname: 'Banner', ... }
Versus a single string case:
"Bruce Banner"
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 19, 2023, 5:38pm UTC](https://discuss.elastic.co/t/mapping-issue/347532/3 "2023-12-19T17:38:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.