# Form Submission Conditions **URL:** \ **Category:** Ask for Help\ **Created:** [December 9, 2022, 8:48pm UTC](https://community.glideapps.com/t/form-submission-conditions/55610 "2022-12-09T20:48:37Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 9, 2022, 9:33pm UTC](https://community.glideapps.com/t/form-submission-conditions/55610/4 "2022-12-09T21:33:05Z")
Check out this post. A custom form is nothing more than a regular detail screen with entry components that update a row in real time…and then a button to add those values to another table. It gives us a lot more freedom for validation. > [@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… I also mention a technique to make a custom form reusable from multiple different screens in the same app. That’s only if you need to reuse the form in multiple places. > [@Auto Archiving, Sanity Check, Reusable Forms, etc](https://community.glideapps.com/t/auto-archiving-sanity-check-reusable-forms-etc/44544): > > I wanted to share a few techniques that I just implemented in my app. A little background…I’m building a process in my app that will replace the email address with a template value. What it does is replace user@email.com with ARCHIVE-user@email.com. The email column is a row owner column. Once ARCHIVE is appended to the email, it becomes an unowned row and is permanently hidden from the app. I’m doing this in an effort to speed up my app by hiding data that’s more than 2 years old. Unowned… Just be aware that the use of a custom form will count against your edit/update counts a lot more than a native form would. --- _[View the full topic](https://community.glideapps.com/t/form-submission-conditions/55610)._