# Data validation best practices

**URL:** https://community.glideapps.com/t/data-validation-best-practices/49924
**Category:** Ask for Help
**Created:** [September 22, 2022, 6:15pm UTC](https://community.glideapps.com/t/data-validation-best-practices/49924 "2022-09-22T18:15:58Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)
#### Post date: [September 22, 2022, 11:29pm UTC](https://community.glideapps.com/t/data-validation-best-practices/49924/2 "2022-09-22T23:29:00Z")

</div>

Best you can do at this point is to create what we like to call “custom forms”

> [@How do I create a custom form?](https://community.glideapps.com/t/how-do-i-create-a-custom-form/25014):
>
> I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using [User Specific Columns](https://docs.glideapps.com/all/reference/data-editor/user-specific-columns) and [Relations](https://docs.glideapps.com/all/reference/data-editor/computed-columns/relation-column) Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particula…

You can then use “match regex” columns on any of those user specific “form” fields to validate data. The result of those regex columns can serve as conditions as to whether the user can see a button to submit the form.

---

_[View the full topic](https://community.glideapps.com/t/data-validation-best-practices/49924)._