# Fix x-axis in Kibana 7.13.2

**URL:** <https://discuss.elastic.co/t/fix-x-axis-in-kibana-7-13-2/277918>\
**Category:** Kibana\
**Created:** [July 6, 2021, 7:13am UTC](https://discuss.elastic.co/t/fix-x-axis-in-kibana-7-13-2/277918 "2021-07-06T07:13:55Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![ghudgins](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ghudgins/32/138532_2.png) [@ghudgins](https://discuss.elastic.co/u/ghudgins)\
**Post date:** [July 7, 2021, 1:10pm UTC](https://discuss.elastic.co/t/fix-x-axis-in-kibana-7-13-2/277918/9 "2021-07-07T13:10:35Z")

</div>

Check out runtime fields in the Lens UI instead of stack management (it's newer as of 7.13) - [Lens | Kibana Guide [7.13] | Elastic](https://www.elastic.co/guide/en/kibana/current/lens.html#add-fields-in-lens)

You can add a script that converts the field to the appropriate data type. Really, though, if this works for you it's more performant to index the appropriate type up front (runtime fields are slower than indexed fields).

Here's an example that does the opposite of what you're trying to do. The example uses painless which exposes a lot of useful java APIs.

```auto
Long input = doc['event.duration'].value;
String output = Objects.toString(input);

emit(output);

```

---

_[View the full topic](https://discuss.elastic.co/t/fix-x-axis-in-kibana-7-13-2/277918)._