# Issue with Multi-value Parameter "Reserved Value": Select All returns 0/False despite setting Custom Value to 'ALL'

**URL:** <https://community.amazonquick.com/t/issue-with-multi-value-parameter-reserved-value-select-all-returns-0-false-despite-setting-custom-value-to-all/51215>\
**Category:** Q&A\
**Tags:** parameters, filters-controls-and-parameters, Business-Intelligence-Engineer\
**Created:** [January 20, 2026, 9:26am UTC](https://community.amazonquick.com/t/issue-with-multi-value-parameter-reserved-value-select-all-returns-0-false-despite-setting-custom-value-to-all/51215 "2026-01-20T09:26:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chanhlm](https://avatars.discourse-cdn.com/v4/letter/c/f4b2a3/32.png) [@chanhlm](https://community.amazonquick.com/u/chanhlm)\
**Post date:** [January 20, 2026, 9:26am UTC](https://community.amazonquick.com/t/issue-with-multi-value-parameter-reserved-value-select-all-returns-0-false-despite-setting-custom-value-to-all/51215/1 "2026-01-20T09:26:12Z")

</div>

Hi all,

I explicitly configured my Multi-value Parameter with **Set reserved value = Custom value: ‘ALL’**.

**The Issue:** When I choose **“Select All”** in the control, it looks like QuickSight is passing `NULL` instead of the string `'ALL'`, ignoring my configuration.

I tested both scenarios in my Calculated Field:

1. `ifelse(in('ALL', ${pCategory}), ...)` → Returns **FALSE** (Unexpected, since I set it to ‘ALL’).

2. `ifelse(in(NULL, ${pCategory}), ...)` → Returns **TRUE** (Works!).

**My Question:** Why is QuickSight ignoring my “Custom Reserved Value” setting and passing `NULL` instead? Has anyone faced this behavior?

 ![image](https://d1wl4jav5dp96l.cloudfront.net/original/3X/a/a/aa92159a42bb5198fbd397f2aabfa1646773387a.png)

 ![image](https://d1wl4jav5dp96l.cloudfront.net/original/3X/a/0/a01d6573dbf357c1effd0655042069a093668003.png)

---

<div class="post-metadata">

**Author:** ![Brett](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/brett/32/36494_2.png) [@Brett](https://community.amazonquick.com/u/Brett)\
**Post date:** [January 20, 2026, 3:52pm UTC](https://community.amazonquick.com/t/issue-with-multi-value-parameter-reserved-value-select-all-returns-0-false-despite-setting-custom-value-to-all/51215/2 "2026-01-20T15:52:36Z")

</div>

Hi @chanhlm,  
Yes, using ‘NULL’ to account for your select all in multi value parameter scenarios is standard with how Quick Sight runs it’s calculations. To my understanding, when select all is chosen, it passes a ‘NULL’ value to the underlying parameter, therefore returning all values. So when building a calculated field to account for the multi-value, you’ll want to continue utilizing the ‘NULL’