Hidden field not showing up in submission

  • Profile Image
    mschmitt
    Asked on October 09, 2015 at 01:49 PM

    Hello,

    I already looked at this forum question (http://www.jotform.com/answers/524046-Hidden-fields-not-showing-in-submission-report) that seemed relevant to my question, but it doesn't because the field I'm concerned with is 'checked' in the settings of submission view. I have a hidden field that is auto-populated in my forms - it is for an internal reference ID so we can track the submissions. However, as I've been testing the form the prepopulated hidden field does not show up when the form is submitted. The IDs are unique for each of 1300 or so prepopulated links, and I need them to come through with the submission. How can I make this happen? A screenshot of the submission from the below link is attached.

     

    The hidden field is highlighted:

    http://form.jotformpro.com/form/52446564402958?description=%7becrmGen=a3Ja0000000TktC&siteName=Ohio%20Department%20of%20Developmental%20Disabilities%20Montgomery%20-%20Huber%20Heights%20-%20OH&siteAddress=7679%20Timbercrest%20Dr.&address2=&city=Huber%20Heights&state69=OH&zip75=45424&genLocation=outside%20on%20side%20of%20Building&generatorName=GEN%201&generatorMake53=Cummins&generatorModel=502FDR7022CCW&generatorSerial=JJ92629-8/3-1&generatorRated50=360&fuelType=Diesel&engineMake54=&engineModel=&engineSerial=&engineManufacture=1979&engineOutput=0&engineOutput38=

  • Profile Image
    david
    Answered on October 09, 2015 at 04:38 PM

    Hi,

    In your pre-populated link, you have:

    http://form.jotformpro.com/form/52446564402958?description=%7becrmGen=a3Ja0000000TktC

    I believe the field is not populating at all.  There does not appear to be a need for
    description=%7

    Removing that portion should allow for the ECRM Gen ID field to show properly.  In my test form, changing the beginning of the link did indeed populate the field properly, even when hidden:

     

  • Profile Image
    mschmitt
    Answered on October 13, 2015 at 09:06 AM

    My links all have description={ in order to encode the URL, as below. However, the '{' becomes '%7b' when the links are used to create hyperlinked text, as will be the case with all of my links. I have tried submitting through both a link where I pasted the URL into the URL bar (the %7b does not appear in the URL) and through clicking one of my hyperlinks ({ is replaced by %7b), and the ECRM ID does not work in either instance.

     

    I had added in 'description={' because I was told I needed to encode the URL. Will I have problems with spaces or other non-alphanumeric characters if I remove it? That seems like it allows the ECRM Gen ID to show up, but I'm worried there will be other side effects.

     

     

     

    http://form.jotformpro.com/form/52446564402958?description={ecrmGen=a3Ja0000000TWxz&siteName=Fannie Mae - Reston, VA - Financial Center&siteAddress=11600 American Dream Way&address2=&city=Reston&state69=VA&zip75=20190&genLocation=&generatorName=&generatorMake53=Caterpillar&generatorModel=3412T&generatorSerial=&generatorRated50=500&fuelType=%232 Fuel Oil (Diesel)&engineMake54=&engineModel=&engineSerial=&engineManufacture=1995&engineOutput=0&engineOutput38=
  • Profile Image
    BDAVID
    Answered on October 13, 2015 at 11:45 AM

    No you will not have problems with spaces or other non-alphanumeric characters if you remove it. If yo haven't used our Field Prepopulator App, here it is: http://apps.jotform.com/app/field_prepopulator

     

  • Profile Image
    mschmitt
    Answered on October 13, 2015 at 01:14 PM

    Ok, thank you for the help. When would I need to encode a URL then?

  • Profile Image
    david
    Answered on October 13, 2015 at 02:27 PM

    URL encoding is necessary where certain characters, such as spaces, are interpreted differently.  For instance, in a query string, the ampersand (&) is used as a separator between key-value pairs. If you were to put an ampersand into one of those values, it would look like the separator between the end of a value and the beginning of the next key. So for special characters like this, we use percent encoding so that we can be sure that the data is unambiguously encoded.

    It all depends on if the character would be interpreted improperly or not. 

    The field pre-populator app does the encoding where needed for you.  There is not need to make further changes.

  • Profile Image
    mschmitt
    Answered on October 13, 2015 at 03:32 PM

    Unfortunately I need around 1700 unique prepopulated URLs, so the prepopulator app won't really work for my situation. I used an Excel template to put them all together with the information I need. I replaced ampersands and and pound symbols with your percent encoding, but am just trying to ensure that the URLs created in my Excel template will work correctly. Most of them have spaces in prepopulated fields. They seem to be working right now, but is this a situation when characters might be interpreted differently?

  • Profile Image
    BDAVID
    Answered on October 13, 2015 at 05:32 PM

    Characters will not be interpreted differently when using the percent encoding, so your forms will continue working fine, if by any chance you see something not working correctly, please let us know, we will be glad to assist you.