# Is it possible to use a (previously created) runtime field in a transform?

**URL:** <https://discuss.elastic.co/t/is-it-possible-to-use-a-previously-created-runtime-field-in-a-transform/296104>\
**Category:** Kibana\
**Tags:** transforms, runtime-fields\
**Created:** [February 2, 2022, 6:02pm UTC](https://discuss.elastic.co/t/is-it-possible-to-use-a-previously-created-runtime-field-in-a-transform/296104 "2022-02-02T18:02:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![colin1](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@colin1](https://discuss.elastic.co/u/colin1)\
**Post date:** [February 2, 2022, 6:02pm UTC](https://discuss.elastic.co/t/is-it-possible-to-use-a-previously-created-runtime-field-in-a-transform/296104/1 "2022-02-02T18:02:14Z")

</div>

Hi,

I'm trying to use kibana's 'transform' gui to aggregate some data.

One of the fields I'd like to aggregate is a runtime field that I created in the index mappings. This field is an integer whose value is set depending on certain conditions (ie. depending on how the document looks/what values I see, I want to count it differently. this logic is captured in the runtime field script).

Issue/question:

In discover/lens I see my runtime field, but when I go to the Kibana Transform ui to create the transform I can't find the field. Does this mean we can't use (pre defined) runtime fields in a transform? I guess that would make sense if these fields aren't calculated till runtime.

ie. I hoped to see my runtime field here and have a choice to use it in aggregations:

 ![Screen Shot 2022-02-02 at 9.59.13 AM](https://us1.discourse-cdn.com/elastic/original/3X/5/7/570400273fb79d6f5b3a495069a2c28c9ee7d9f5.png)

Is there maybe a different/better approach within the gui? Maybe i should be using this option instead of creating the runtime field ahead of time? Wasn't able to find documentation on exactly how this is used.

 ![Screen Shot 2022-02-02 at 10.00.51 AM](https://us1.discourse-cdn.com/elastic/original/3X/3/4/34b6a98879824da63b5cb8d7350f838386143e6a.png)

Happy to provide more detail as needed, just trying to keep my question specific in case theres an easy answer. Thanks for any help!

---

<div class="post-metadata">

**Author:** ![Quynh\_Nguyen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quynh_nguyen/32/97817_2.png) [@Quynh\_Nguyen](https://discuss.elastic.co/u/Quynh_Nguyen)\
**Post date:** [February 2, 2022, 6:09pm UTC](https://discuss.elastic.co/t/is-it-possible-to-use-a-previously-created-runtime-field-in-a-transform/296104/2 "2022-02-02T18:09:05Z")

</div>

Hi Colin,

The GUI should support runtime fields created in the index mappings. It's also possible that the runtime fields are available but hidden. Can you expand the `95 columns hidden` and check if the runtime fields you're looking are listed there? If so, toggling them on should work.

If you don't see them listed in the `95 columns hidden` dropdown, then do you mind sharing what version of Kibana are you on?

Thanks!

---

<div class="post-metadata">

**Author:** ![colin1](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@colin1](https://discuss.elastic.co/u/colin1)\
**Post date:** [February 2, 2022, 6:13pm UTC](https://discuss.elastic.co/t/is-it-possible-to-use-a-previously-created-runtime-field-in-a-transform/296104/3 "2022-02-02T18:13:55Z")

</div>

Hi Quynh,

Thanks for confirming it should work and for the fast response!

So its now showing, not sure what happened haha. I swear I refreshed? Maybe something weird about using multiple tabs lol. Anyway working now! Thanks 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 2, 2022, 6:14pm UTC](https://discuss.elastic.co/t/is-it-possible-to-use-a-previously-created-runtime-field-in-a-transform/296104/4 "2022-03-02T18:14:09Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
