# \[BUG-15977\] Lookup Expression Not Allowing Null or None for noMatchValue

**URL:** <https://forum.inductiveautomation.com/t/bug-15977-lookup-expression-not-allowing-null-or-none-for-nomatchvalue/32012>\
**Category:** Ignition Early Access\
**Tags:** ignition80\
**Created:** [February 6, 2020, 7:16pm UTC](https://forum.inductiveautomation.com/t/bug-15977-lookup-expression-not-allowing-null-or-none-for-nomatchvalue/32012 "2020-02-06T19:16:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![WillMT10](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@WillMT10](https://forum.inductiveautomation.com/u/WillMT10)\
**Post date:** [February 6, 2020, 7:16pm UTC](https://forum.inductiveautomation.com/t/bug-15977-lookup-expression-not-allowing-null-or-none-for-nomatchvalue/32012/1 "2020-02-06T19:16:27Z")

</div>

We are in the process of testing an upgrade of our gateway from 7.9 to 8.0.7. We have a number of expression tags in our main UDT performing lookup expression functions. In 7.9 the lookup function would accept null or none as a noMatchValue, but all of these same tags error out in 8.0 with Error\_ExpressionEval(“java.lang.NullPointerException”). Even if there is a good result in the dataset for the lookup function to find, it will still throw this error. Upon changing the noMatchValue to a non-null value, all expressions run fine and return the desired results - except for not being able to set to null/none when a value doesn’t exist.

---

<div class="post-metadata">

**Author:** ![WillMT10](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@WillMT10](https://forum.inductiveautomation.com/u/WillMT10)\
**Post date:** [February 6, 2020, 7:38pm UTC](https://forum.inductiveautomation.com/t/bug-15977-lookup-expression-not-allowing-null-or-none-for-nomatchvalue/32012/2 "2020-02-06T19:38:19Z")

</div>

Some new insight on this issue. If the lookup expression cannot find the value, it uses the the noMatchValue properly - even if it is set to none - and does not throw an error. It only throws an error when noMatchValue is set to none AND the lookup function finds a result in the dataset.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 7, 2020, 4:45pm UTC](https://forum.inductiveautomation.com/t/bug-15977-lookup-expression-not-allowing-null-or-none-for-nomatchvalue/32012/3 "2020-02-07T16:45:55Z")

</div>

Filed. Should be an easy fix.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 2, 2020, 7:28pm UTC](https://forum.inductiveautomation.com/t/bug-15977-lookup-expression-not-allowing-null-or-none-for-nomatchvalue/32012/4 "2020-03-02T19:28:21Z")

</div>

This issue is fixed in 8.0.10.