Changing the Field's Unique Name

  • lcallander
    Asked on March 5, 2018 at 6:34 PM

    In following the instructions in this thread:

    https://www.jotform.com/answers/1121183-Changing-the-field-unique-name

    For how to change a field's unique name, I have discovered that this does not exactly work.  For some reason, JotForm is still adding a prefix to the field name upon output.  See screenshot of code inspection.  Name is still showing as "q20_USOURCE"

    I am trying to pass variables to this hidden field, and I cannot.  Please advise.  I have many forms that this needs to happen on.  Here is a link to one of them:

    Jotform Thread 1405791 Screenshot
  • John_Benson
    Replied on March 5, 2018 at 8:49 PM

    You can change the Field Name in the Properties window. Here's a guide:

    https://www.jotform.com/help/146-How-to-Find-Field-IDs-and-Names

    After that, save the form and if the issue still persists, let us know. Thank you.

  • lcallander
    Replied on March 5, 2018 at 8:56 PM

    John, please read my question.  I have already done that - as that is the same instruction in the discussion link I added. 

    If you would please look at my form, you would see that is already done.  My issue is that JotForm is putting a prefix on the name that is unwanted.  I do not want this prefix.  If you compare my form settings with the published form, you will see what I am referencing.

  • Nik_C
    Replied on March 6, 2018 at 1:50 AM

    I see what you mean, a prefix is added to field name automatically, and that, I'm afraid, cannot be changed. 

    What you could do though, is to download the Full source code of the form and edit the field names right there in the code, then you will have to upload the code to some online domain (since you cannot upload it back to the Form builder).

    Let us know if that could work for you.

    Thank you!

  • lcallander
    Replied on March 6, 2018 at 11:30 AM

    Bummer!  Thanks Nik for answering my specific question!  I was afraid that the custom HTML form was going to be the answer. :-(

    Is this something that can be looked into for the future?

  • liyam
    Replied on March 6, 2018 at 12:27 PM

    Unfortunately, I don't think they would make any change on that part of the process, as the prefix on fields is necessary for the uniqueness of each field added.

    If you wish to prepopulate the field using URL parameters, just exclude the prefix, on your field's case, just use USOURCE (exclude the prefix until the underscore). Or if you can give us an idea on how this field is getting prepopulated, perhaps we can find other means on how to implement the process that you have in mind.

    Thanks.