# Kibana 8.4.2 new Control does not show options for runtime field **URL:** \ **Category:** Kibana\ **Created:** [September 23, 2022, 12:38pm UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015 "2022-09-23T12:38:24Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Jonas\_S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonas_s/32/97631_2.png) [@Jonas\_S](https://discuss.elastic.co/u/Jonas_S)\ **Post date:** [September 23, 2022, 12:38pm UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/1 "2022-09-23T12:38:24Z")
Hello, i upgraded to the newest Kibana version to use the new Controls. I have a runtime field in my Data View that gets a value from the indexname: ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/f/4f181cf21d73a99d9c5172607aade5db0756a15b.png) It can be used in all visualizations without problems. I tried to add a Control for it: ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/6/6662f40bd3f7bf03be0e819d1b5336bbc6b3bdf0.png) But it does not show any options: ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/a/6a594cd93fcaf114a68a0bba97037f91423f7c46.png) Is this still an issue with the new Controls? Best regards Jonas ---
**Author:** ![Jonas\_S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonas_s/32/97631_2.png) [@Jonas\_S](https://discuss.elastic.co/u/Jonas_S)\ **Post date:** [September 26, 2022, 10:02am UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/2 "2022-09-26T10:02:11Z")
I tried it with the deprecated input controls and it is working as expected: ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/8/88487074f0fd88b19100934c32826e33f2c94d95.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/c/ecacffe4b7cf6bb038165d377d8032fbd1277ba0.png) So this seems to be a problem with the new Controls. Best regards Jonas ---
**Author:** ![Jonas\_S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonas_s/32/97631_2.png) [@Jonas\_S](https://discuss.elastic.co/u/Jonas_S)\ **Post date:** [October 4, 2022, 11:39am UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/3 "2022-10-04T11:39:31Z")
Am i the only one having this issue? Is it known? I can not find any further information. ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 5, 2022, 3:18am UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/4 "2022-10-05T03:18:33Z")
Agree I would expect it to be there.... I tested with a runtime I defined in the data view I saw the same behavior... not showing in dropdown. I added to the actual mapping and it worked bug / feature I asked internally, but that would be the work around. ```auto PUT discuss-test/_mapping { "runtime": { "new_dept_value": { "type": "keyword", "script": { "source": """emit((doc['dept'].value) + " : " + (doc['value'].value))""" } } } } ``` And it worked as expected.... ![Screen Shot 2022-10-04 at 8.17.45 PM](https://us1.discourse-cdn.com/elastic/original/3X/8/1/81f94aec018306b8093d52f3e40e8330fd55c23b.png) ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 5, 2022, 2:32pm UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/5 "2022-10-05T14:32:26Z")
Hi @Jonas_S Update:There is already an issues to get this solved, I can not promise a release but I was told it was "prioritized" > > > \*\*Describe the feature:\*\* The new controls currently do not support scripted / r…untime fields. Support for this feature should be added. ---
**Author:** ![Jonas\_S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonas_s/32/97631_2.png) [@Jonas\_S](https://discuss.elastic.co/u/Jonas_S)\ **Post date:** [October 6, 2022, 12:13pm UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/6 "2022-10-06T12:13:52Z")
Thanks, i didn't even know you could give a source script for a field mapping. So is this a scripted field which will be deprecated in the future, or a runtime field, or neither? Best regards Jonas ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 6, 2022, 1:14pm UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/7 "2022-10-06T13:14:58Z")
Hi @Jonas_S That above is a new runtime field... Basically the newer better version of a scripted field and is the go forward method. > **[Map a runtime field | Elasticsearch Guide \[8.4\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime-mapping-fields.html)** ---
**Author:** ![cpu](https://avatars.discourse-cdn.com/v4/letter/c/919ad9/32.png) [@cpu](https://discuss.elastic.co/u/cpu)\ **Post date:** [October 24, 2022, 8:18am UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/8 "2022-10-24T08:18:44Z")
Me too... I'm on v8.4.3 of ES. I switched to new controls as "suggested" by the GUI and discovered for this issue... A little bit surprise of this. I hope this will be solved ASAP. Thank you for any effort the Elastic Team can put on this fix! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 21, 2022, 8:19am UTC](https://discuss.elastic.co/t/kibana-8-4-2-new-control-does-not-show-options-for-runtime-field/315015/9 "2022-11-21T08:19:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.