# True/False won't work on QuickSearch

**URL:** <https://www.epiusers.help/t/true-false-wont-work-on-quicksearch/133515>\
**Category:** Kinetic ERP\
**Tags:** quick-search\
**Created:** [March 20, 2026, 12:58am UTC](https://www.epiusers.help/t/true-false-wont-work-on-quicksearch/133515 "2026-03-20T00:58:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SteveM](https://www.epiusers.help/letter_avatar_proxy/v4/letter/s/a183cd/32.png) [@SteveM](https://www.epiusers.help/u/SteveM)\
**Post date:** [March 20, 2026, 12:58am UTC](https://www.epiusers.help/t/true-false-wont-work-on-quicksearch/133515/1 "2026-03-20T00:58:10Z")

</div>

I’m trying to setup a filter on a QuickSearch with a True/False value but I cannot get it to work.  
This is what the BAQ calculated field looks like  
 ![image](https://www.epiusers.help/uploads/default/original/3X/2/7/27dc18b8b4245b3aa3be26eecdefa3e7debc918a.png)  
This is how the QuickSearch is setup

 ![image](https://www.epiusers.help/uploads/default/original/3X/5/8/5821998a8eaa314538023563809e6608e41b78da.png)  
But if the user select either in the filter no results are returned.

I have tried all variants of Upper and Lower case

How do I get it to work?

Thanks  
Steve

---

<div class="post-metadata">

**Author:** ![mkubiczek](https://www.epiusers.help/letter_avatar_proxy/v4/letter/m/dc4da7/32.png) [@mkubiczek](https://www.epiusers.help/u/mkubiczek)\
**Post date:** [March 20, 2026, 8:34am UTC](https://www.epiusers.help/t/true-false-wont-work-on-quicksearch/133515/2 "2026-03-20T08:34:00Z")

</div>

This is a complete shot in the dark as I haven’t used quick search, but did you try 1 and 0 for your value? I have seen instances where true/false is interpreted as 1/0.

P.S. Also, true/false are keywords, not strings, so in your calculated field expression you do not enclose them in quotes.

---

<div class="post-metadata">

**Author:** ![kananga](https://www.epiusers.help/user_avatar/www.epiusers.help/kananga/32/80812_2.png) [@kananga](https://www.epiusers.help/u/kananga)\
**Post date:** [March 20, 2026, 1:53pm UTC](https://www.epiusers.help/t/true-false-wont-work-on-quicksearch/133515/3 "2026-03-20T13:53:19Z")

</div>

> [@mkubiczek](#):
>
> 1 and 0

👆 This is (usually) the way.

Boolean true/false is normally stored as a `bit`, 1 or 0. But, “normal” is not a design requirement. Database design often gets punted to web devs and they make weird things instead of looking for what already exists. Booleans are at least fairly reliably stored as `bit` though, so 1/0 is a great place to start.

Date/time are a crapshoot though. Datatypes `date` and `time` and `datetime` and `datetimeoffset` exist but those values commonly get stored as `string` and `decimal` and `int` and etc. and that means you get to solve a little puzzle when you’re filtering or comparing.

\*_edit_ - not a dig at Epicor specifically. Commercial software and data standards are different universes. They look alike in a lot of ways but you can tell commercial software apart because it has a goatee.