# How to keep form values

**URL:** <https://community.glideapps.com/t/how-to-keep-form-values/69310>\
**Category:** Ask for Help\
**Created:** [January 6, 2024, 8:24pm UTC](https://community.glideapps.com/t/how-to-keep-form-values/69310 "2024-01-06T20:24:23Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [January 8, 2024, 3:29pm UTC](https://community.glideapps.com/t/how-to-keep-form-values/69310/4 "2024-01-08T15:29:46Z")

</div>

Bonjour Ludovic, jette un coup d’oeil à la vidéo suivante. Elle explique bien certain comportements des formulaires natifs dans Glide (form screen ou form container). Pas certain que cela t’aide directement, mais peut-être.

Les formulaires custom sont pratiques car on contrôle de façon granulaire ce qui s’y passe, mais attention, ce n’est pas vraiment un formulaire, c’est en fait une detail screen déguisée en formulaire. En particulier, les custom forms consomment plusieurs updates par soumission, alors qu’un formulaire natif ne consomme qu’un update lors de l’unique clique sur le bouton submit/envoyer.

> [@sparkle Understanding (and hacking) Form Screens](https://community.glideapps.com/t/understanding-and-hacking-form-screens/69309):
>
> wave Hey fellow Gliders! Form screens (or form containers) in Glide are critical when creating apps that allow users to add new data (projects, tasks, posts, etc.) to your database. Navigating form screens requires some understanding of screen and table relationships and involves some mental juggling when configuring visibility conditions within the form. In this video, I peel back the layers of a form screen to show you how they work and how to work around a couple of the commonly frustratin…

---

_[View the full topic](https://community.glideapps.com/t/how-to-keep-form-values/69310)._