https://legacy.forums.gravityhelp.com/topic/saving-fields-individually-vs-saving-form-entirely Gravity Support Forums Topic: Saving Fields individually vs Saving Form entirely en-US Sat, 04 Apr 2026 18:18:58 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/saving-fields-individually-vs-saving-form-entirely#post-68331 Sat, 28 Jul 2012 09:01:59 +0000 sc0ttkclark 68331@https://legacy.forums.gravityhelp.com/ <p>I was wondering if you guys could explain the benefits and UX point of view you as plugin authors have experienced with the Saving All Fields approach. What I mean is, there are a few ways:</p> <p>1. When a user clicks add new or edit field buttons/links, they are given a button like 'Update' or 'Save Field', which sends an AJAX request to save it</p> <p>2. When a user clicks 'Save Form', all field data is sent to be saved.</p> <p>3. When a user does anything, AJAX updates are sent as they change individual settings and/or options</p> <p>It appears you guys do #2. I'm specifically wondering how that's performing and if you experienced any issues during the support and development of Gravity Forms with UX or PHP/JS limitations. </p>