# Multiple rows per user e-mail

**URL:** <https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659>\
**Category:** Ask for Help\
**Created:** [November 19, 2020, 9:34am UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659 "2020-11-19T09:34:57Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![M\_Rom](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/m_rom/32/340_2.png) [@M\_Rom](https://community.glideapps.com/u/M_Rom)\
**Post date:** [November 19, 2020, 9:34am UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/1 "2020-11-19T09:34:57Z")

</div>

Recently, I’ve found that my user sign-up tab is creating multiple rows for the same e-mail address. The first row is always blank and the second row has the profile information that the user filled out. The sign-up page is only accessible when the user is first signing up for the application and after filling out certain fields, they have access to their profile page. Because the first row in my Google sheets is the blank version of their profile, they can’t move on from the signup page.  
This was working well not that long ago and I haven’t made any significant tweaks to this aspect so I’m not sure what’s going on.  
Anyone with ideas of why this is happening and where I might have gone wrong?

---

<div class="post-metadata">

**Author:** ![Rosewebstudio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rosewebstudio/32/12261_2.png) [@Rosewebstudio](https://community.glideapps.com/u/Rosewebstudio)\
**Post date:** [November 19, 2020, 9:43am UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/2 "2020-11-19T09:43:24Z")

</div>

Perhaps this is a related post? Have you searched the forum?

> [@Users Duplicated](https://community.glideapps.com/t/users-duplicated/18008/9):
>
> Si lo hacen a través de un form no están editando, están creando otro usuario, por eso te aparecen duplicados alomejor. Como dice @ThinhDinh tiene que ser con el lápiz de arriba a la derecha

---

<div class="post-metadata">

**Author:** ![M\_Rom](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/m_rom/32/340_2.png) [@M\_Rom](https://community.glideapps.com/u/M_Rom)\
**Post date:** [November 19, 2020, 10:00am UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/3 "2020-11-19T10:00:12Z")

</div>

That’s probably what’s going on, thanks!

Would be great to have a workaround. Within the “landing” tab, I have two form buttons that they user can click based on why they want to use the application which was a nice little feature but if this is the case then I’ll have to change it up.

---

<div class="post-metadata">

**Author:** ![Rosewebstudio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rosewebstudio/32/12261_2.png) [@Rosewebstudio](https://community.glideapps.com/u/Rosewebstudio)\
**Post date:** [November 19, 2020, 10:10am UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/4 "2020-11-19T10:10:49Z")

</div>

Hope you get to work it out 🙂

---

<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:** [November 19, 2020, 11:03am UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/5 "2020-11-19T11:03:03Z")

</div>

Do you use a form for them to fill out the details, or you use tab visibility for an onboarding process?

---

<div class="post-metadata">

**Author:** ![M\_Rom](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/m_rom/32/340_2.png) [@M\_Rom](https://community.glideapps.com/u/M_Rom)\
**Post date:** [November 19, 2020, 11:10am UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/6 "2020-11-19T11:10:11Z")

</div>

Actually, I’m pretty sure I figured out a work around, rather than using the “form” button, I set the button to be “link to screen”. This just edits the row rather than creating a new one.

---

<div class="post-metadata">

**Author:** ![Rosewebstudio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rosewebstudio/32/12261_2.png) [@Rosewebstudio](https://community.glideapps.com/u/Rosewebstudio)\
**Post date:** [November 19, 2020, 11:33am UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/7 "2020-11-19T11:33:00Z")

</div>

Well done… 👍

---

<div class="post-metadata">

**Author:** ![PabloMFalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pablomfalero/32/31166_2.png) [@PabloMFalero](https://community.glideapps.com/u/PabloMFalero)\
**Post date:** [November 19, 2020, 12:47pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/8 "2020-11-19T12:47:10Z")

</div>

Sorry, its in Spanish. Translation is available upon request!! 😀

---

<div class="post-metadata">

**Author:** ![Rosewebstudio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rosewebstudio/32/12261_2.png) [@Rosewebstudio](https://community.glideapps.com/u/Rosewebstudio)\
**Post date:** [November 19, 2020, 1:13pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/9 "2020-11-19T13:13:19Z")

</div>

Lol 😂

---

<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:** [November 19, 2020, 1:40pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/10 "2020-11-19T13:40:42Z")

</div>

Just for future users who read this thread, forms will always create a new row, so what you want for a profile sign-up process is to have tab visibility + increment button, not a form.

---

<div class="post-metadata">

**Author:** ![M\_Rom](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/m_rom/32/340_2.png) [@M\_Rom](https://community.glideapps.com/u/M_Rom)\
**Post date:** [November 19, 2020, 2:48pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/11 "2020-11-19T14:48:08Z")

</div>

This question should probably go to a different thread, but I’ve created two buttons at the bottom of my “linked screen”. One of these buttons is grayed out and exists when the data in entry options aren’t filled out. The other is colored and is open when they’re all filled out --\> once you click this button, it sends you back to your profile and increments.  
What’s strange is that the grayed out button disappears when only 1 of the 6 visibility conditions are satisfied. This isn’t the case for the virtually identical (but opposite conditions) colored button. In both circumstances, I’m using “AND”.  
Any thoughts as to why this might be happening?

---

<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:** [November 19, 2020, 2:53pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/12 "2020-11-19T14:53:37Z")

</div>

Can you share screenshots of the visibility conditions for both buttons?

---

<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:** [November 19, 2020, 3:02pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/13 "2020-11-19T15:02:18Z")

</div>

It should be.

Grayed button: A is empty OR B is empty,… , F is empty =\> No action

Colored button: A is not empty AND B is not empty… , F is not empty =\> Increment action

---

<div class="post-metadata">

**Author:** ![M\_Rom](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/m_rom/32/340_2.png) [@M\_Rom](https://community.glideapps.com/u/M_Rom)\
**Post date:** [November 19, 2020, 3:04pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/14 "2020-11-19T15:04:02Z")

</div>

![Screen Shot 2020-11-19 at 3.02.33 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/3/330b7ce3bc71eac043d14ff8cbef3f4ecd43153b.png) ![Screen Shot 2020-11-19 at 3.00.14 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/3/f35bff50dd9a266106cf1757fe60e3060136f877.png)

---

<div class="post-metadata">

**Author:** ![M\_Rom](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/m_rom/32/340_2.png) [@M\_Rom](https://community.glideapps.com/u/M_Rom)\
**Post date:** [November 19, 2020, 3:07pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/15 "2020-11-19T15:07:28Z")

</div>

That works, although I’m not sure I fully understand the logic of having to be OR since if x is full AND y is empty then the conditions still aren’t satisfied or what’s a better way of understanding this?

---

<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:** [November 19, 2020, 4:16pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/16 "2020-11-19T16:16:58Z")

</div>

> A is empty OR B is empty,… , F is empty

If any of them is empty then the grayed button appears.

> A is not empty AND B is not empty… , F is not empty

If all of them are not empty then the colored button appears.

---

<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:** [November 19, 2020, 4:59pm UTC](https://community.glideapps.com/t/multiple-rows-per-user-e-mail/18659/17 "2020-11-19T16:59:32Z")

</div>

With an ‘AND’, ALL conditions have to be met before the condition can be true.  
With an ‘OR’, only ONE condition needs to be met before the condition can be true.
