# Write to an Exsisting Row

**URL:** <https://community.glideapps.com/t/write-to-an-exsisting-row/23459>\
**Category:** Ask for Help\
**Created:** [February 26, 2021, 7:09am UTC](https://community.glideapps.com/t/write-to-an-exsisting-row/23459 "2021-02-26T07:09:23Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [March 1, 2021, 6:23am UTC](https://community.glideapps.com/t/write-to-an-exsisting-row/23459/13 "2021-03-01T06:23:48Z")

</div>

> [@Jen\_NYCP](#):
>
> Thanks Darren! So I can’t just use the promotions sheet and redemptions sheet for this? The user profile sheet has to be included as well?

Are you trying to implement what I had suggested here…?

> [@Track Button Click by Signed In User](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/29):
>
> Just in case the answer to this is yes, here is what I would do: Drop the idea of a boolean in your User Profiles sheet, as you won’t need it Create a new table/sheet, call it something like “Redemptions” This table will contain one row per user, per offer redeemed, and should contain least 3 columns: User ID (a value that uniquely identifies each user, and will allow you to create a relation back to your User Profiles sheet. I’d recommend using the RowID) Offer ID (same as above, but to you…

That’s essentially a “3 table” solution: Users, Promotions & Redemptions  
So yes, there needs to be a relation between Users & Redemptions, as that’s how you track which users have redeemed which promotions.

The [link](https://community.glideapps.com/t/global-announcements-with-user-tracking-copyable/23422) I gave you earlier today is an alternative “2 table” solution, which doesn’t require a separate Redemptions table. The differences:

- 3 Table Solution:
  - Easier to understand and implement
  - But, costly in terms of row count. The Redemptions table requires one row per user, per Promotion redeemed. So for example, imagine you have 100 promotions and 100 users, and every user redeems each of the 100 promotions. That’s 10,000 rows.

- 2 Table Solution:
  - More complicated and slightly more difficult to implement.
  - But, much more efficient in terms of row count. Only one row per Promotion is required, regardless of the number of users. So 100 promotions and 100 users (or 100,000 users) will only use 100 rows.

> [@Jen\_NYCP](#):
>
> The initial ‘redeemed’ data adds perfectly with the add row action to the sheet, then comes the addiiton of the ‘used’ data which would just need to be tied to the same user AND promo. When I added the ‘used’ column, it actually wrote to the first instance of the promotion, which was for another user and not the user who clicked ‘used’ for that promotion.

You probably won’t like me saying this, but the easiest way to solve that would be to apply row owners, so that each user only has access to their own redemptions 🙂

---

_[View the full topic](https://community.glideapps.com/t/write-to-an-exsisting-row/23459)._