# Add new screen already populated?

**URL:** <https://community.glideapps.com/t/add-new-screen-already-populated/34620>\
**Category:** Ask for Help\
**Created:** [November 16, 2021, 7:47pm UTC](https://community.glideapps.com/t/add-new-screen-already-populated/34620 "2021-11-16T19:47:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\
**Post date:** [November 16, 2021, 7:50pm UTC](https://community.glideapps.com/t/add-new-screen-already-populated/34620/2 "2021-11-16T19:50:32Z")

</div>

I think you’d be better off using a “Show Form Screen” action.

The way you have it set up, it is simply pulling the information from the first row of the Data source you have selected (Trades).

If you’d like to use something other than a Form screen, you’ll need to use a Custom Form and create placeholder columns to store your entry fields, then pass them through to the Trades table using a button with an action.

> [@How do I create a custom form?](https://community.glideapps.com/t/how-do-i-create-a-custom-form/25014):
>
> I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using [User Specific Columns](https://docs.glideapps.com/all/reference/data-editor/user-specific-columns) and [Relations](https://docs.glideapps.com/all/reference/data-editor/computed-columns/relation-column) Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particula…

---

_[View the full topic](https://community.glideapps.com/t/add-new-screen-already-populated/34620)._
