# The preprocessing for selecting values does not work in discover

**URL:** https://discuss.elastic.co/t/the-preprocessing-for-selecting-values-does-not-work-in-discover/384951
**Category:** Kibana
**Tags:** discover
**Created:** [February 6, 2026, 8:34pm UTC](https://discuss.elastic.co/t/the-preprocessing-for-selecting-values-does-not-work-in-discover/384951 "2026-02-06T20:34:52Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Ruslan\_Hafizov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruslan_hafizov/32/139786_2.png) [@Ruslan\_Hafizov](https://discuss.elastic.co/u/Ruslan_Hafizov)
#### Post date: [February 6, 2026, 8:34pm UTC](https://discuss.elastic.co/t/the-preprocessing-for-selecting-values-does-not-work-in-discover/384951/1 "2026-02-06T20:34:52Z")

</div>

When selecting a field in the left menu, no selection is displayed by field. Despite the fact that the value itself is in the index. I couldn't find information in the documentation on how this function works to check what it outputs via the api. I assume it has to do with the index. When choosing a different Dataview, the problem persists. I would like to know how this feature works in kibana and what are the possible reasons for this result.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/5/e5046ee4069c0c19b8ba2905a82ada2709b143ad.png)

---

<div class="post-metadata">

### Author: ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)
#### Post date: [February 7, 2026, 1:52am UTC](https://discuss.elastic.co/t/the-preprocessing-for-selecting-values-does-not-work-in-discover/384951/2 "2026-02-07T01:52:06Z")

</div>

Hello @Ruslan_Hafizov

Could you please share the ELK version?

There was similar issue reported as shared in below post :

> <https://github.com/elastic/kibana/issues/148140>
>
> \*\*Kibana version:\*\*
> 8.5.x
> 
> \*\*Describe the bug:\*\*
> When there's a mapping like… \`epoch\_second\` used for the timefield used in the data view, the requests returning the field statistics of Discover's field list fail:
> \`\`\`
> failed to parse date field \[2007-12-28T08:28:29.697Z\] with format \[epoch\_second\]: \[failed to parse date field \[2007-12-28T08:28:29.697Z\] with format \[epoch\_second\]\]"
> \`\`\`
> 
> The requests for the statistics needs to have \`"format": "strict\_date\_optional\_time"\` in the range to work correctly 
> 
> 
> \*\*Steps to reproduce:\*\*
> 1. Create demo data with a timestamp like this \`\`\`"timestamp":
> {
> "type": "date",
> "format": "epoch\_second"
> }\`\`\`
> 2. Go to Discover and create an data view for the demo data
> 3. When showing the field popover there's just a message \`No field data for the current search.\`
> !\[Discover\_-\_Elastic\](https://user-images.githubusercontent.com/463851/209788618-307aed04-f22c-484b-b14f-d9ec5d231a07.png)
> 
> \*\*Expected behavior:\*\*
> In the popover there should be a list of the Top10 field values

Thanks!!

---

<div class="post-metadata">

### Author: ![Ruslan\_Hafizov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruslan_hafizov/32/139786_2.png) [@Ruslan\_Hafizov](https://discuss.elastic.co/u/Ruslan_Hafizov)
#### Post date: [February 7, 2026, 8:00am UTC](https://discuss.elastic.co/t/the-preprocessing-for-selecting-values-does-not-work-in-discover/384951/3 "2026-02-07T08:00:02Z")

</div>

Hi, thanks for the reply. My elasticsearch version is 8.13.4 and the kibana version is 8.7.0. I tried using discover:showLegacyFieldTopValues, but it didn't help.  
UPD: I'm sorry, I applied the settings to the wrong space. discover:showLegacyFieldTopValues solves the problem