# Custom Action Delete Row

**URL:** <https://community.glideapps.com/t/custom-action-delete-row/37278>\
**Category:** Feature Requests\
**Created:** [January 16, 2022, 7:53pm UTC](https://community.glideapps.com/t/custom-action-delete-row/37278 "2022-01-16T19:53:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 16, 2022, 7:53pm UTC](https://community.glideapps.com/t/custom-action-delete-row/37278/1 "2022-01-16T19:53:39Z")

</div>

Hi, I can add a custom action to delete a row, rather than use the built-in delete. My reason for doing so is to log the delete to another table to save some of the information off, and record who deleted the record.

_HOWEVER_, I lose the ability to have a confirmation on the delete row action. There is a “show notification” but I don’t see any way to make the notification contingent confirm/cancel.

---

<div class="post-metadata">

**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\
**Post date:** [January 16, 2022, 8:14pm UTC](https://community.glideapps.com/t/custom-action-delete-row/37278/2 "2022-01-16T20:14:23Z")

</div>

You’d have to set up two buttons — the first is a delete button that toggles a value. The 2nd button is only visible after the first button is pressed. Your delete row action would be on the 2nd button to act as a confirmation to delete.

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 16, 2022, 8:32pm UTC](https://community.glideapps.com/t/custom-action-delete-row/37278/3 "2022-01-16T20:32:40Z")

</div>

So actually three buttons. One says delete, and then two pop up “Confirm / Cancel”?

Thank you, I will give that a go. My only concern is that if they leave the app that flag stays set and they will see the two buttons again the next time they come in. Not sure how to account for that.

---

<div class="post-metadata">

**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\
**Post date:** [January 16, 2022, 8:34pm UTC](https://community.glideapps.com/t/custom-action-delete-row/37278/4 "2022-01-16T20:34:17Z")

</div>

Yes, sorry, one button and one button bar!

The way that I mitigate the issue of the field being chosen next time they enter is that I clear the value when they enter this screen initially (usually through an inline list action, for example). If this is your highest level screen, that may not be possible though.

---

<div class="post-metadata">

**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\
**Post date:** [January 16, 2022, 8:41pm UTC](https://community.glideapps.com/t/custom-action-delete-row/37278/5 "2022-01-16T20:41:33Z")

</div>

Well, I am using a floating button, so it worked best for me to add two additional floating buttons.

One thing I found is that if instead of confirm/cancel, I select the actions at the top to cancel or done, it clears the value for me! I am using a user-specific field as my flag so users do not interfere with each other.

Thank you again.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [January 17, 2022, 8:42pm UTC](https://community.glideapps.com/t/custom-action-delete-row/37278/6 "2022-01-17T20:42:32Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
