# Getting a no\_viable\_alt\_exception only when trying to filter using a scripted field

**URL:** <https://discuss.elastic.co/t/getting-a-no-viable-alt-exception-only-when-trying-to-filter-using-a-scripted-field/183145>\
**Category:** Kibana\
**Tags:** painless\
**Created:** [May 28, 2019, 4:23pm UTC](https://discuss.elastic.co/t/getting-a-no-viable-alt-exception-only-when-trying-to-filter-using-a-scripted-field/183145 "2019-05-28T16:23:47Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ebalmeida](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebalmeida/32/47103_2.png) [@ebalmeida](https://discuss.elastic.co/u/ebalmeida)\
**Post date:** [June 11, 2019, 2:39pm UTC](https://discuss.elastic.co/t/getting-a-no-viable-alt-exception-only-when-trying-to-filter-using-a-scripted-field/183145/7 "2019-06-11T14:39:44Z")

</div>

I created another post [here](https://discuss.elastic.co/t/safe-numerical-return-value-in-scripted-fields-avoiding-null-pointers-in-filters-using-scripted-fields/184816) to reference null pointers in filters using scripted fields.

---

_[View the full topic](https://discuss.elastic.co/t/getting-a-no-viable-alt-exception-only-when-trying-to-filter-using-a-scripted-field/183145)._