# \[Express-Sequelize\] Smart-field search based on mutation

**URL:** <https://community.forestadmin.com/t/express-sequelize-smart-field-search-based-on-mutation/5812>\
**Category:** Help me!\
**Created:** [January 10, 2023, 2:51pm UTC](https://community.forestadmin.com/t/express-sequelize-smart-field-search-based-on-mutation/5812 "2023-01-10T14:51:11Z")\
**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:** [January 10, 2023, 2:51pm UTC](https://community.forestadmin.com/t/express-sequelize-smart-field-search-based-on-mutation/5812/1 "2023-01-10T14:51:11Z")

</div>

Hello,

I created a [pull request](https://github.com/ForestAdmin/forest-express-sequelize/pull/1058) to make clear `smart-field` `search` use returned value instead of mutation on `query`

With this proposal the idea is to match with type definition and doc, but it can break the search without `return query`

---

<div class="post-metadata">

**Author:** ![Alban\_Bertolini](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/alban_bertolini/32/1077_2.png) [@Alban\_Bertolini](https://community.forestadmin.com/u/Alban_Bertolini)\
**Post date:** [January 11, 2023, 10:33am UTC](https://community.forestadmin.com/t/express-sequelize-smart-field-search-based-on-mutation/5812/2 "2023-01-11T10:33:47Z")

</div>

Hello,  
I answered you on the PR 🙂  
Thank you for this contribution.