# Kibana scripted field used in interactive control shows no data

**URL:** https://discuss.elastic.co/t/kibana-scripted-field-used-in-interactive-control-shows-no-data/208934
**Category:** Kibana
**Created:** [November 21, 2019, 4:35pm UTC](https://discuss.elastic.co/t/kibana-scripted-field-used-in-interactive-control-shows-no-data/208934 "2019-11-21T16:35:42Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![jmcclure](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@jmcclure](https://discuss.elastic.co/u/jmcclure)
#### Post date: [November 21, 2019, 4:35pm UTC](https://discuss.elastic.co/t/kibana-scripted-field-used-in-interactive-control-shows-no-data/208934/1 "2019-11-21T16:35:42Z")

</div>

Hi,

(Elastic stack version 6.7.1 on Centos 7.6 OS)

I have a dashboard that utilizes a control visualization, which specifies a field that is defined in Kibana as a scripted field. I have document data going into Elasticsearch, however, the control does not return any items for the drop down list control to display.

When I configure the Kibana discover app using filtering for the fields used in the scripted field, I am getting a response with data.

I've double checked mappings, etc. The scripted field is defined using only keywords. Really don't understand why the control shows no data. Any suggestions on where/what to check or what can possibly be causing this behavior?

Thanks.

James

Scripted Field:

 ![scripted_field](https://us1.discourse-cdn.com/elastic/original/3X/3/2/3264232ffdf0fbc91f483212cb941ab33da9e777.png)

Control Visualization:

 ![control_vis](https://us1.discourse-cdn.com/elastic/original/3X/4/2/4267770495514035357eba4efd6ab0e148848bff.png)

Discover app:

 ![discover_filter](https://us1.discourse-cdn.com/elastic/original/3X/6/e/6ed9bfd137a995ce99602ff006208e238f48a97b.png)

Dashboard:

 ![dashboard_no_dropdown](https://us1.discourse-cdn.com/elastic/original/3X/c/1/c17fea28992e35ca4e8a2e38c653363e59a5c5bf.png)

---

<div class="post-metadata">

### Author: ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)
#### Post date: [November 21, 2019, 4:52pm UTC](https://discuss.elastic.co/t/kibana-scripted-field-used-in-interactive-control-shows-no-data/208934/2 "2019-11-21T16:52:27Z")

</div>

This is a popular topic today 🙂

> [@Options list in Controls-Visualization doesn't work properly with scripted field as type static lookup](https://discuss.elastic.co/t/options-list-in-controls-visualization-doesnt-work-properly-with-scripted-field-as-type-static-lookup/208882/2):
>
> Hey @marlich, It looks like you ran into a known limitation with Input Controls: [https://github.com/elastic/kibana/issues/17340](https://github.com/elastic/kibana/issues/17340) Unfortunately, I'm not aware of a way to accomplish what you're trying to do, other than to reindex your data.

This is unfortunately a known limitation with Input Controls: [Input controls don't work with scripted fields · Issue #17340 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/17340)

---

<div class="post-metadata">

### Author: ![jmcclure](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@jmcclure](https://discuss.elastic.co/u/jmcclure)
#### Post date: [November 21, 2019, 5:07pm UTC](https://discuss.elastic.co/t/kibana-scripted-field-used-in-interactive-control-shows-no-data/208934/3 "2019-11-21T17:07:37Z")

</div>

I've had this configuration in place for ES 6.0.0 and 6.2.4 with no issues being reported. Upgraded to 6.7.1 in April and have several issues raised with this behavior.

If you are saying that [https://github.com/elastic/kibana/issues/17340](https://github.com/elastic/kibana/issues/17340) indicates this configuration is not supported, then I am ok with that. i can move this stuff into a pipeline.

---

<div class="post-metadata">

### Author: ![Larry\_Gregory](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/larry_gregory/32/34969_2.png) [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)
#### Post date: [November 21, 2019, 5:15pm UTC](https://discuss.elastic.co/t/kibana-scripted-field-used-in-interactive-control-shows-no-data/208934/4 "2019-11-21T17:15:09Z")

</div>

Thanks for the additional information - I'll add this to the linked issue; that might help the engineers triage this further. I wasn't aware it used to work. For the time being, I'd suggest moving into a pipeline if that's a viable option for you.

---

<div class="post-metadata">

### Author: ![jmcclure](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@jmcclure](https://discuss.elastic.co/u/jmcclure)
#### Post date: [November 21, 2019, 5:21pm UTC](https://discuss.elastic.co/t/kibana-scripted-field-used-in-interactive-control-shows-no-data/208934/5 "2019-11-21T17:21:23Z")

</div>

It's not a hard failing issue. Been installing stuff from scratch over and over to see if I could identify any causes... Sometimes it works, sometimes not. 🙁

---

<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: [December 19, 2019, 5:27pm UTC](https://discuss.elastic.co/t/kibana-scripted-field-used-in-interactive-control-shows-no-data/208934/6 "2019-12-19T17:27:00Z")

</div>

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