# Array text filter not use altered value

**URL:** <https://community.forestadmin.com/t/array-text-filter-not-use-altered-value/5218>\
**Category:** Help me!\
**Created:** [September 6, 2022, 10:17am UTC](https://community.forestadmin.com/t/array-text-filter-not-use-altered-value/5218 "2022-09-06T10:17:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Justin\_Martin](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/justin_martin/32/1028_2.png) [@Justin\_Martin](https://community.forestadmin.com/u/Justin_Martin)\
**Post date:** [September 6, 2022, 10:17am UTC](https://community.forestadmin.com/t/array-text-filter-not-use-altered-value/5218/1 "2022-09-06T10:17:04Z")

</div>

Hello,

I am on forest-express-sequelize, I am using a text array field with modified values. In the filter, when I select my field and write my value, it sends my query with the specified value.

Instead of sending a query with the source value associated to the one I indicated (if it is found). So I have to use a source value that"

Config:  
 ![Capture d’écran 2022-09-06 à 12.08.39](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/7/741653194417f59110c269c00b451db327bfd358.png)

Valid filter (actually):

 ![Capture d’écran 2022-09-06 à 12.07.47](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/5/5c42ace3d6ac0cd3f006d2b084536b8ab540fa3d.png)

Expected filter:

 ![Capture d’écran 2022-09-06 à 12.08.02](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/7/749ee6ab1eeb9579db763b6ac8440cf642e1ebce.png)

---

<div class="post-metadata">

**Author:** ![anon34731316](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@anon34731316](https://community.forestadmin.com/u/anon34731316)\
**Post date:** [September 7, 2022, 12:20pm UTC](https://community.forestadmin.com/t/array-text-filter-not-use-altered-value/5218/2 "2022-09-07T12:20:34Z")

</div>

Hello @Justin_Martin,

Thanks for your message.

I totally understand your point. You are not the first one to bring this up.  
I’m pushing your request in our Product board, and hopefully we’ll make this change soon.

Cheers!
