# Search on collection is sending an error - sequelize-typescript UUID are interpreted as string

**URL:** <https://community.forestadmin.com/t/search-on-collection-is-sending-an-error-sequelize-typescript-uuid-are-interpreted-as-string/4025>\
**Category:** Help me!\
**Tags:** typescript\
**Created:** [January 14, 2022, 4:19pm UTC](https://community.forestadmin.com/t/search-on-collection-is-sending-an-error-sequelize-typescript-uuid-are-interpreted-as-string/4025 "2022-01-14T16:19:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![anon94532230](https://avatars.discourse-cdn.com/v4/letter/a/a587f6/32.png) [@anon94532230](https://community.forestadmin.com/u/anon94532230)\
**Post date:** [January 17, 2022, 8:57am UTC](https://community.forestadmin.com/t/search-on-collection-is-sending-an-error-sequelize-typescript-uuid-are-interpreted-as-string/4025/2 "2022-01-17T08:57:03Z")

</div>

Hi @NicolasF !  
As you can see [here](https://community.forestadmin.com/t/enable-to-research-on-a-specific-table/2038/13), other people fixed this issue by using UUID as the datatype of their field in the models.  
Can you try to do the same ?

---

_[View the full topic](https://community.forestadmin.com/t/search-on-collection-is-sending-an-error-sequelize-typescript-uuid-are-interpreted-as-string/4025)._