# Mutate convert seems not to be working
**URL:** https://discuss.elastic.co/t/mutate-convert-seems-not-to-be-working/128566
**Category:** Logstash
**Created:** [April 18, 2018, 3:23pm UTC](https://discuss.elastic.co/t/mutate-convert-seems-not-to-be-working/128566 "2018-04-18T15:23:52Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@widhalmt](https://discuss.elastic.co/u/widhalmt)
#### Post date: [April 18, 2018, 3:23pm UTC](https://discuss.elastic.co/t/mutate-convert-seems-not-to-be-working/128566/1 "2018-04-18T15:23:52Z")
Hi,
I had a mutate filter convert some nested fields from string to float.
It worked before the last update to 6.2.4 but now it seems to have stopped working. Unfortunately I skipped some versions and don't know anymore what version it worked with, but it was a 6.x.
```auto
mutate {
convert => {
"[a][b]" => "integer"
"[a][c]" => "integer"
}
}
```
Curiosusly I couldn't get it to work even when I changed the nested fields to non-nested fields. The convert is just ignored and the values are written to Elasticsearch as string. I triple checked with the documentation and had a coworker have a look at it but still no luck. Either I'm blind or this stopped working. I didn't find an issue in the GitHub Repo of mutate either.
Could you just give me a hint?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 16, 2018, 3:24pm UTC](https://discuss.elastic.co/t/mutate-convert-seems-not-to-be-working/128566/2 "2018-05-16T15:24:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.