# User entries won't be written into data table

**URL:** <https://community.glideapps.com/t/user-entries-wont-be-written-into-data-table/61055>\
**Category:** Ask for Help\
**Created:** [April 27, 2023, 12:51pm UTC](https://community.glideapps.com/t/user-entries-wont-be-written-into-data-table/61055 "2023-04-27T12:51:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pluzgi](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pluzgi/32/56533_2.png) [@pluzgi](https://community.glideapps.com/u/pluzgi)\
**Post date:** [April 27, 2023, 12:51pm UTC](https://community.glideapps.com/t/user-entries-wont-be-written-into-data-table/61055/1 "2023-04-27T12:51:06Z")

</div>

Hello there,

I’m playing around with our first app and have the following problems/questions:

1. If a user (after sign-in) fills in data into the fields in our profile form only part of their data will be written into the glide table (it happens for choices fields and text entry fields). Is this a common problem?
2. Can i hide the “Required” word? It’s distracting somehow.
3. I can’t add an additional action after the “Submit” action. Is that intended or do i miss something?

 ![Bildschirmfoto 2023-04-27 um 14.44.05](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/9/5914ba315ff1dc2336623294c111cf9c0b764a5e.jpeg)

Thanks a lot for your support and have a lovely day,  
Sabine

---

<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:** [April 27, 2023, 12:58pm UTC](https://community.glideapps.com/t/user-entries-wont-be-written-into-data-table/61055/2 "2023-04-27T12:58:29Z")

</div>

You are using a form container, which will add a new row upon submission.  
That’s not what you want, because if the User has signed in, then they will already have a row in your User Profiles table. What you should use instead is an Edit Form.  
Also, you shouldn’t need to ask the to enter their email address, as that will already have been captured with their first sign in.

---

<div class="post-metadata">

**Author:** ![pluzgi](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pluzgi/32/56533_2.png) [@pluzgi](https://community.glideapps.com/u/pluzgi)\
**Post date:** [April 27, 2023, 2:08pm UTC](https://community.glideapps.com/t/user-entries-wont-be-written-into-data-table/61055/3 "2023-04-27T14:08:18Z")

</div>

Thanks, Darren.  
When i choose a new form screen, the template uses a form container. Is that not intended for profile set up?  
And, can i hide the “Required” word? I saw somewhere that apps here had the “\*” instead.

 ![Bildschirmfoto 2023-04-27 um 16.06.11](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/e/de7dba504fbd957c4c4a1b1cd6a0c1a76f5b1c12.jpeg)

---

<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:** [April 27, 2023, 2:18pm UTC](https://community.glideapps.com/t/user-entries-wont-be-written-into-data-table/61055/4 "2023-04-27T14:18:25Z")

</div>

> [@pluzgi](#):
>
> When i choose a new form screen, the template uses a form container. Is that not intended for profile set up?

No, it’s not.  
As I said, a Form Screen/Container will add a new row, and that’s not what you want in this case.  
I would suggest adding a button to one of your existing screens, and use a “Show User Profile Screen” action. You can then add whatever input components to that screen that you need.

> [@pluzgi](#):
>
> Can i hide the “Required” word? It’s distracting somehow.

If you do it as I describe above, then you won’t need to worry about that.

> [@pluzgi](#):
>
> I can’t add an additional action after the “Submit” action. Is that intended or do i miss something?

Form screens don’t support onSubmit actions, but again - you shouldn’t be using a form screen for that.
