# Filter table data

**URL:** <https://forum.inductiveautomation.com/t/filter-table-data/64087>\
**Category:** General Discussion\
**Tags:** perspective\
**Created:** [September 15, 2022, 12:50am UTC](https://forum.inductiveautomation.com/t/filter-table-data/64087 "2022-09-15T00:50:48Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![mdemaris](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mdemaris/32/54639_2.png) [@mdemaris](https://forum.inductiveautomation.com/u/mdemaris)\
**Post date:** [September 15, 2022, 9:07pm UTC](https://forum.inductiveautomation.com/t/filter-table-data/64087/11 "2022-09-15T21:07:25Z")

</div>

Here is the thread I mentioned, and after reading it again, perhaps using a stored proc might be the way to go as SQL Server does allow using NULL.

> [@Pass Wildcard Parameters on Named Queries](https://forum.inductiveautomation.com/t/pass-wildcard-parameters-on-named-queries/34594/6):
>
> LIKE doesn’t work for integer columns, only for string columns. I would make another named query. IA isn’t charging you for extra ones, after all. smile

---

_[View the full topic](https://forum.inductiveautomation.com/t/filter-table-data/64087)._