# Custom Action - Set Columns - Delete Row

**URL:** <https://community.glideapps.com/t/custom-action-set-columns-delete-row/27009>\
**Category:** Ask for Help\
**Created:** [May 20, 2021, 12:30pm UTC](https://community.glideapps.com/t/custom-action-set-columns-delete-row/27009 "2021-05-20T12:30:24Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [May 20, 2021, 7:01pm UTC](https://community.glideapps.com/t/custom-action-set-columns-delete-row/27009/7 "2021-05-20T19:01:57Z")

</div>

ok. I found your old post about that issue.

> [@Custom cart - buy button - this item is no longer available](https://community.glideapps.com/t/custom-cart-buy-button-this-item-is-no-longer-available/26218):
>
> can anyone help advice why I get this message (item no longer available) when I use the buy button? for the product info in the configuration panel: I have used basic text columns for Name, Description, Product ID and basic number column for price. image empty. could it be because the buy button is in a screen based on data from the Orders Sheet not the Products Sheet ? are buy buttons only to be placed in product details? appreciate any help here is a link

I also found this much older post that seems to contradict that theory and only indicates that there would be an issue if a user is not signed in and doesn’t have a row to reference.

> [@Buy Button Transaction Error: "this item is no longer available"](https://community.glideapps.com/t/buy-button-transaction-error-this-item-is-no-longer-available/5785/6):
>
> Actually, @Math_X, this isn’t an issue on our end so much as it is something we did not design the Buy Button for. This is unfortunately an incompatibility between how you’ve set up your data and how you’ve configured your buy screen. Your buy screen is trying to read a “Purchase ID” from the SIGN UP sheet to indicate which product is being purchased. However, this same SIGN UP sheet uses our Row Ownership feature. So if you’ve never signed in before, and you do not have a row in this sheet, we…

But more experienced people agree that you can’t do it with Row Owners enabled.

> [@Payment problem with buy button (Stripe)](https://community.glideapps.com/t/payment-problem-with-buy-button-stripe/6379/19):
>
> You can’t have row owners, and all data passed to Stripe needs to be stored in google sheets (nothing can be user specific or in Glide columns).

So, I guess I’m not really sure. I’ve never used the Buy Button myself outside of some very brief testing to see how it works. The main thing I know about the buy button is that it can’t use computed columns. Beyond that, I have no idea what else is required for it to work correctly.

Anyway, have you tried moving your delete before any other action? I know it seems wrong, but it may be something to try.

I’m not finding it right now, but I seem to recall a post a while back that mentioned the pointer to the row getting lost sometimes depending on what actions your are doing. That theory doesn’t make sense though since your Set Column action still works. It may just be a bug with the Delete action since others have had issues too. You may want to submit a bug to [https://glide-help.zendesk.com/hc/en-us/requests/new](https://glide-help.zendesk.com/hc/en-us/requests/new).

---

_[View the full topic](https://community.glideapps.com/t/custom-action-set-columns-delete-row/27009)._