# Use Form button for existing row

**URL:** <https://community.glideapps.com/t/use-form-button-for-existing-row/17254>\
**Category:** Feature Requests\
**Created:** [October 17, 2020, 10:18am UTC](https://community.glideapps.com/t/use-form-button-for-existing-row/17254 "2020-10-17T10:18:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Killko](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/killko/32/39538_2.png) [@Killko](https://community.glideapps.com/u/Killko)\
**Post date:** [October 17, 2020, 10:18am UTC](https://community.glideapps.com/t/use-form-button-for-existing-row/17254/1 "2020-10-17T10:18:18Z")

</div>

It would be very useful to have an option allowing to use the form button to add information to an existing row, rather than always creating a new one.

The alternative is clunky as input fields cannot currently be set as “required” outside of a form or an edit page…

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [October 17, 2020, 10:23am UTC](https://community.glideapps.com/t/use-form-button-for-existing-row/17254/2 "2020-10-17T10:23:34Z")

</div>

If you’re talking specifically about an onboarding experience, I have an example here.

> [@Copyable: A Tribute To Chadwick Boseman & The World Of Randomness](https://community.glideapps.com/t/copyable-a-tribute-to-chadwick-boseman-the-world-of-randomness/15768):
>
> Hi Gliders, it has been a while since I shared my last tutorial and I plan to do this once in a while, so here’s my next one. You can view my previous post here: Techniques used in this app: Tab visibility for sign up process Random value from single value column to change image & quote on homepage Combining multiple random values and use split text for gamification Conditional visibility + Cloudinary for a quiz-like experience App link: For this post, I make an app to pay tribute to M…

Basically combine a number column with tab visibility, then set an increment button to only appear when all required fields have been filled.

---

<div class="post-metadata">

**Author:** ![Killko](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/killko/32/39538_2.png) [@Killko](https://community.glideapps.com/u/Killko)\
**Post date:** [October 18, 2020, 9:28am UTC](https://community.glideapps.com/t/use-form-button-for-existing-row/17254/3 "2020-10-18T09:28:37Z")

</div>

Hi @ThinhDinh yes, I had already implemented onboarding in a similar way. 🙂  
I was looking at adding a COVID pre-visit registration and so looking at adding more details into the user’s account. Obviously I can do it the same way, but it’s much less user-friendly than having a clear notice which fields are required, and more conditional object visibility handling. A form button that acts on an existing row would be so much cleaner…

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [October 18, 2020, 11:52am UTC](https://community.glideapps.com/t/use-form-button-for-existing-row/17254/4 "2020-10-18T11:52:23Z")

</div>

Sounds like you need to use a form button to submit the entries to a log of sorts, and then for each user on the user profile tab, grab the information that was submitted last (multiple relation \> single value whole row of “end”) given that your log sheet will always be sorted where latest entries add new row at bottom.

---

<div class="post-metadata">

**Author:** ![Killko](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/killko/32/39538_2.png) [@Killko](https://community.glideapps.com/u/Killko)\
**Post date:** [October 20, 2020, 10:49am UTC](https://community.glideapps.com/t/use-form-button-for-existing-row/17254/5 "2020-10-20T10:49:34Z")

</div>

Yes, that works for me. Thanks @Robert_Petitto!
