PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Form Capture - Naming The Form Fields

  1. I'm trying to capture form submission. GF is auto-naming the form fields input_1_1, input_1_2, input_2, is_submit_3 (e.t.c.).

    Ideally I'd like to have nice field names, so if (for example) the fields are moved around, I don't have to update the capture. Is this possible?

    Posted 9 years ago on Monday December 6, 2010 | Permalink
  2. Changing the field names (aka field ids) is a messy business that will most likely end in misery and regret. With that said, fear not! Once a field has been created, it's field id will never change. This means changing the order of the fields will not impact the field id. Hope this is helpful! :)

    Posted 9 years ago on Monday December 6, 2010 | Permalink
  3. Not as helpful as one might hope! :( But it does make my job somewhat less tricky :)

    May I suggest a method by which something like this is possible. Perhaps an additional 'field' on the admin screen allowing one to add a 'fieldname' property. This fieldname property could be sent with the form submission, allowing capture to map fieldname with input field name (or 'field id' as you call it).

    Using my example above, the data would be a bit like:
    GFfieldname_input_1 = 'newspaper'
    input_1_1 = 'daily blag'
    input_1_3 = 'weekly blag'
    GFfieldname_input_2 = 'hidden-date'
    input_2 = 'YYYY/MM/DD'

    Event better, as it is a WP plugin, you could add the GFfieldname properties in using apply_filter on the results, and in turn allow theme/plugin builders to hook into that for 'form capture', rather than rely on parsing $_POST ?

    Posted 9 years ago on Tuesday December 7, 2010 | Permalink
  4. Interesting idea... Not sure if we will decide to implement it, but I will bring this up in our brainstorming sessions.
    Thanks the suggestion!

    Posted 9 years ago on Tuesday December 7, 2010 | Permalink
  5. This is a good idea, and it seems like it would be a simple thing to do. I guess you'd have to build in something that disallows duplicate fieldnames.

    I have a form that must integrate with an established database, so the fieldnames are critical. And believe it or not, the database manager is unwilling to change the fieldnames to match the ones GF generates. Without the ability to manage fieldnames in Gravity Forms, I'll have to create the form by hand. Ugh! Thought that was behind me.

    Posted 9 years ago on Friday May 27, 2011 | Permalink
  6. Out of curiosity, how did the brainstorming go?

    Posted 8 years ago on Thursday September 22, 2011 | Permalink