# Ability to check for typos against previous entries? **URL:** \ **Category:** General\ **Created:** [June 3, 2025, 2:20pm UTC](https://community.epicollect.net/t/ability-to-check-for-typos-against-previous-entries/1073 "2025-06-03T14:20:30Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Elena](https://community.epicollect.net/letter_avatar_proxy/v4/letter/e/278dde/32.png) [@Elena](https://community.epicollect.net/u/Elena)\ **Post date:** [June 3, 2025, 2:20pm UTC](https://community.epicollect.net/t/ability-to-check-for-typos-against-previous-entries/1073/1 "2025-06-03T14:20:30Z")
### Project Name (if applicable, otherwise just type n/a) EWYT field data ### Question Is there a way, when entering a microchip number, to check if a similar or the same number already exists in a previous entry, so I can make sure I am not entering a typo and then unintentionally creating a second identity? For example, if there is a microchip number X041A848484 (X041A is the prefix of all the microchip numbers) that already has several entries, how can I ensure I do not accidentally type 848485 and thus this entry will be treated as a different animal than it is intended. Is there a way to select from a database of already existing microchip numbers? ### I confirm I have read the User Guide at [docs.epicollect.net](http://docs.epicollect.net) on ### I confirm I have searched for an answer in this community. on ---
**Author:** ![Epicollect5](https://community.epicollect.net/user_avatar/community.epicollect.net/epicollect5/32/2653_2.png) [@Epicollect5](https://community.epicollect.net/u/Epicollect5)\ **Post date:** [June 9, 2025, 8:53am UTC](https://community.epicollect.net/t/ability-to-check-for-typos-against-previous-entries/1073/2 "2025-06-09T08:53:41Z")
> **[Uniqueness | Epicollect5 User Guide](https://docs.epicollect.net/formbuilder/uniqueness)** > > Many times on a survey the answer to a question needs to be unique. For example a class code, a student ID, a patient NHS number, and so on. ---
**Author:** ![Elena](https://community.epicollect.net/letter_avatar_proxy/v4/letter/e/278dde/32.png) [@Elena](https://community.epicollect.net/u/Elena)\ **Post date:** [June 16, 2025, 6:59am UTC](https://community.epicollect.net/t/ability-to-check-for-typos-against-previous-entries/1073/3 "2025-06-16T06:59:26Z")
![Screenshot_20250613_123210_Epicollect5](https://discourse-space.fra1.digitaloceanspaces.com/original/2X/1/11444ce836f17304d2fb49b141c754dcc874f0cc.jpeg) Thank you for your response but this solution doesn’t resolve my query exactly. In the attached screenshot, you can see I need to enter a PIT\_tag number. The 5 digit prefix is already included, and I need to enter a six digit suffix. I am searching for a way to verify that my entry is genuinely new or if there is a previous entry with a similar suffix. This is to check for typos and check if I am entering a new or old PIT tag. I hope that makes more sense than my first query? ---
**Author:** ![Epicollect5](https://community.epicollect.net/user_avatar/community.epicollect.net/epicollect5/32/2653_2.png) [@Epicollect5](https://community.epicollect.net/u/Epicollect5)\ **Post date:** [June 16, 2025, 7:01am UTC](https://community.epicollect.net/t/ability-to-check-for-typos-against-previous-entries/1073/4 "2025-06-16T07:01:57Z")
> I am searching for a way to verify that my entry is genuinely new That is solved by setting the uniqueness constraint. * * * To match a specific pattern have a look at regex > **[Add Questions | Epicollect5 User Guide](https://docs.epicollect.net/formbuilder/add-inputs#regex)** ---
**Author:** ![Epicollect5](https://community.epicollect.net/user_avatar/community.epicollect.net/epicollect5/32/2653_2.png) [@Epicollect5](https://community.epicollect.net/u/Epicollect5)\ **Post date:** [June 16, 2025, 7:11am UTC](https://community.epicollect.net/t/ability-to-check-for-typos-against-previous-entries/1073/5 "2025-06-16T07:11:42Z")
> there a way to select from a database of already existing microchip numbers? If you already have the microchip numbers you can list them in a SEARCH question > **[Search | Epicollect5 User Guide](https://docs.epicollect.net/formbuilder/search)** > > The SEARCH question type behaves like an autocomplete search bar.