# Any tutorial/resource showing a full project build using Glide pages **URL:** \ **Category:** Ask for Help\ **Created:** [March 29, 2023, 11:04am UTC](https://community.glideapps.com/t/any-tutorial-resource-showing-a-full-project-build-using-glide-pages/59838 "2023-03-29T11:04:30Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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 30, 2023, 12:05pm UTC](https://community.glideapps.com/t/any-tutorial-resource-showing-a-full-project-build-using-glide-pages/59838/6 "2023-03-30T12:05:30Z")
> [@siraj-samsudeen](#): > > Can you please provide some link to the other approaches Probably easier if I describe the approach. Firstly, you need to use a Custom Form. A good description of what that is is given below: > [@Multi-step form](https://community.glideapps.com/t/multi-step-form/34556/4): > > A custom form is just a detail screen that’s designed to act like a form and uses entry components linked to user specific columns as the temporary placeholders for the data. Once you are done filling out the form, you can have a button with a custom action that will first have an Add Row action that will take those user specific column values and write them to a different table. You can then follow that action with a Set Column action that will clear the user specific columns so it’s ready fo… I would recommend creating a single row table ([Helper Table](https://community.glideapps.com/t/how-would-you-describe-a-helper-table/54497)) to use to drive the form. All columns in the helper table should be user specific. The key point is that you need an action that first sets a unique value in a column in the helper table as the form is opened. This value is used as a UUID for both the parent record as well as the child records. Your custom form serves the purpose of both creating the parent record and adding N child records in the same screen. You need to use visibility conditions to show either the parent record entry inputs, or the child record inputs. This can be conditional on the state of a relation between the UUID and the child records table. That is, if the relation is empty then show the parent record inputs. Once the parent record is created, the relation will no longer be empty and so you switch to the child record creation inputs. You can dynamically show the added child records using a collection component with the aforementioned relation as a source. That’s essentially the guts of it. Obviously there is a bit more to it than that, and there will be specific details related to the exact user experience that you want to achieve. --- _[View the full topic](https://community.glideapps.com/t/any-tutorial-resource-showing-a-full-project-build-using-glide-pages/59838)._