# Custom Action for a Form Return to Screen **URL:** \ **Category:** Ask for Help\ **Created:** [January 17, 2023, 11:05pm UTC](https://community.glideapps.com/t/custom-action-for-a-form-return-to-screen/56814 "2023-01-17T23:05:30Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [January 18, 2023, 8:03am UTC](https://community.glideapps.com/t/custom-action-for-a-form-return-to-screen/56814/4 "2023-01-18T08:03:47Z")
I’m not exactly sure, but my guess would be that the Delete Row action fails because the form screen is not attached to any row, so there is nothing to delete. Regardless, this is not a reliable way to prevent duplicate entries. The best way to prevent duplicates is with a Custom Form. With a custom form, your form inputs are first written to user specific columns. This allows you to detect a duplicate _before_ the form is submitted, and use conditional logic to prevent the user from submitting the form. > [@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… --- _[View the full topic](https://community.glideapps.com/t/custom-action-for-a-form-return-to-screen/56814)._