# Building custom forms & user specific values

**URL:** <https://community.glideapps.com/t/building-custom-forms-user-specific-values/58945>\
**Category:** Ask for Help\
**Created:** [March 9, 2023, 9:11am UTC](https://community.glideapps.com/t/building-custom-forms-user-specific-values/58945 "2023-03-09T09:11:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\
**Post date:** [March 9, 2023, 9:11am UTC](https://community.glideapps.com/t/building-custom-forms-user-specific-values/58945/1 "2023-03-09T09:11:48Z")

</div>

I am recently switching between having

- user specific columns on the row that determine what custom form is to be opened

to having

- user specific columns only on the user profile table/row that determine what form and components to show

reason include

- I don’t feeling comfortable with user specific data on large tables in every row if not really necessary until we get more insights on every user’s data size etc…
- its seems simpler

are there any disadvantages to this change? or is it no difference or possibly an advantage?

---

<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:** [March 10, 2023, 12:29am UTC](https://community.glideapps.com/t/building-custom-forms-user-specific-values/58945/2 "2023-03-10T00:29:37Z")

</div>

Without knowing exactly what your data structure is, I don’t think there are any huge advantages or disadvantages in doing that. Personally I use one-line tables to help with creating custom forms, since I don’t want those columns to be in the User Profiles table (too many to manage).

I’m not likely to use those values for any other cases other than adding a row, so I don’t need to access it as a user profiles column.

---

<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 10, 2023, 1:17am UTC](https://community.glideapps.com/t/building-custom-forms-user-specific-values/58945/3 "2023-03-10T01:17:10Z")

</div>

> [@ThinhDinh](#):
>
> Personally I use one-line tables to help with creating custom forms, since I don’t want those columns to be in the User Profiles table (too many to manage).
> 
> I’m not likely to use those values for any other cases other than adding a row, so I don’t need to access it as a user profiles column.

This ☝