# Cannot filter on Agency more than once in Setting

**URL:** <https://primero.supporthub.dev/forum/t/cannot-filter-on-agency-more-than-once-in-setting/509>\
**Category:** CPIMS\
**Tags:** v2-0\
**Created:** [December 22, 2021, 9:02pm UTC](https://primero.supporthub.dev/forum/t/cannot-filter-on-agency-more-than-once-in-setting/509 "2021-12-22T21:02:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![irlawrence](https://primero.supporthub.dev/forum/user_avatar/primero.supporthub.dev/irlawrence/32/8_2.png) [@irlawrence](https://primero.supporthub.dev/forum/u/irlawrence)\
**Post date:** [December 22, 2021, 9:02pm UTC](https://primero.supporthub.dev/forum/t/cannot-filter-on-agency-more-than-once-in-setting/509/1 "2021-12-22T21:02:45Z")

</div>

On 2.2.1 I filter users by Agency. After I apply the first time it works. Any subsequent changes of Agency do not filter and I get this in the console

```auto
 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'merge')
    at onSubmit (application.77c7932afd7d19f94ecc.js:1)
    at application.77c7932afd7d19f94ecc.js:1
    at vendor.f1d547cee9c183ffc313.js:3

```

---

<div class="post-metadata">

**Author:** ![jpanchalingam](https://primero.supporthub.dev/forum/user_avatar/primero.supporthub.dev/jpanchalingam/32/73_2.png) [@jpanchalingam](https://primero.supporthub.dev/forum/u/jpanchalingam)\
**Post date:** [December 23, 2021, 4:33pm UTC](https://primero.supporthub.dev/forum/t/cannot-filter-on-agency-more-than-once-in-setting/509/2 "2021-12-23T16:33:09Z")

</div>

Thanks Ian. I’ve added this to the next round of UAT for bug fixes.

---

<div class="post-metadata">

**Author:** ![jack.miszencin](https://primero.supporthub.dev/forum/letter_avatar_proxy/v4/letter/j/90ced4/32.png) [@jack.miszencin](https://primero.supporthub.dev/forum/u/jack.miszencin)\
**Post date:** [January 10, 2022, 5:03pm UTC](https://primero.supporthub.dev/forum/t/cannot-filter-on-agency-more-than-once-in-setting/509/3 "2022-01-10T17:03:15Z")

</div>

Note that this issue should be resolved as of v2.2.2.