# Custom Action for a Form Return to Screen

**URL:** <https://community.glideapps.com/t/custom-action-for-a-form-return-to-screen/56814>\
**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:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roland\_Foster\_Jr](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/roland_foster_jr/32/52576_2.png) [@Roland\_Foster\_Jr](https://community.glideapps.com/u/Roland_Foster_Jr)\
**Post date:** [January 17, 2023, 11:05pm UTC](https://community.glideapps.com/t/custom-action-for-a-form-return-to-screen/56814/1 "2023-01-17T23:05:30Z")

</div>

When editing a form a condition is failed and the else logic kicks in. In that logic the glide action is to return to form. The action return to screen (form) returns to a totally new form page and not the one I just left. Im I missing a configuration here.

---

<div class="post-metadata">

**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:** [January 17, 2023, 11:52pm UTC](https://community.glideapps.com/t/custom-action-for-a-form-return-to-screen/56814/2 "2023-01-17T23:52:59Z")

</div>

Same questions. It seems like you are not using the best approach.

> [@Does Delete row work for Free Version of App](https://community.glideapps.com/t/does-delete-row-work-for-free-version-of-app/56808/4):
>
> A native Add/Edit Form will always add a row or edit a row. Any ‘On Submit’ actions are extra after the row has been added or edited. I very rarely use the ‘On Submit’ action. I think it would help to better understand what you are trying to do, and why you have an extra custom action ‘On Submit’. What are your custom action conditions checking for? The fact that you have a Delete action immediately following an Add action, leads me to believe that something isn’t set up correctly.

---

<div class="post-metadata">

**Author:** ![Roland\_Foster\_Jr](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/roland_foster_jr/32/52576_2.png) [@Roland\_Foster\_Jr](https://community.glideapps.com/u/Roland_Foster_Jr)\
**Post date:** [January 18, 2023, 7:44am UTC](https://community.glideapps.com/t/custom-action-for-a-form-return-to-screen/56814/3 "2023-01-18T07:44:22Z")

</div>

This is a follow up to the action.

 ![GlideApps-CustomAction](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/e/bedb784044fb7b9243b2c4f12179b93f005a9df1.jpeg)  
explanation of the issue.

Delete Row does not work.  
Show Form Screen does not return to Edit Screen.

---

<div class="post-metadata">

**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")

</div>

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…