# Named Query exception Handle

**URL:** <https://forum.inductiveautomation.com/t/named-query-exception-handle/36888>\
**Category:** Ignition\
**Tags:** database, ignition80, vision, scripting\
**Created:** [July 21, 2020, 5:15am UTC](https://forum.inductiveautomation.com/t/named-query-exception-handle/36888 "2020-07-21T05:15:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kudrot.elahi](https://avatars.discourse-cdn.com/v4/letter/k/3d9bf3/32.png) [@kudrot.elahi](https://forum.inductiveautomation.com/u/kudrot.elahi)\
**Post date:** [July 21, 2020, 5:15am UTC](https://forum.inductiveautomation.com/t/named-query-exception-handle/36888/1 "2020-07-21T05:15:03Z")

</div>

Hi, I am trying to fetch data corresponding to selected alarm. It works good, as soon as it finds data from the Named Query-\> Table. But if data is not found it gives error message. I looked all the way to handle exception in Named Query, but could not find any.  
Q1. Is it possible to suppress error message?  
Q2. In the ‘Alarm Class’ instead of showing integer value, is it possible to to show corresponding ‘High’, ‘Low’, ‘Medium’… ?( I am using groupConcat({Root Container.Alarm Status Table.selectedAlarms}, “Priority”, “/”) to fetch value in Alarm Status Table.

 ![Named query exception handle](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/d/cd62e8339c28aac9d77bc2b2e905cb245361c72f.jpeg) ![If Alarm data exist in table](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/d/3d89de5eca7a79acd73e394dba80c679712ca5df.jpeg) ![Selected Alarm Not in the Table](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/f/af11060398fc5cb397511b35284df26751c26d07.jpeg)

---

<div class="post-metadata">

**Author:** ![kudrot.elahi](https://avatars.discourse-cdn.com/v4/letter/k/3d9bf3/32.png) [@kudrot.elahi](https://forum.inductiveautomation.com/u/kudrot.elahi)\
**Post date:** [July 23, 2020, 2:18am UTC](https://forum.inductiveautomation.com/t/named-query-exception-handle/36888/2 "2020-07-23T02:18:57Z")

</div>

In the Authoring page, I just had to select Scalar Query for Query type option. This solved my problem…
