Classic Forms: Fields names are always on lowercase ignoring settings when sending POST data.

  • Profile Image
    paulsapio
    Asked on March 15, 2018 at 01:18 PM

    I am having to send a post data though jot form to a client and their system only accepts uppercase field names. I remapped all the fields to uppercase, but the post is still coming though as lower case - 


    (see attached image and below post back data) 


    a:27:{s:13:"submission_id";s:19:"3969432506804012350";s:6:"formID";s:14:"80710745428962";s:2:"ip";s:13:"98.177.150.86";s:8:"location";s:8:"lasvegas";s:13:"appointmentor";s:11:"Appointment";s:6:"date18";a:6:{i:0;s:2:"03";i:1;s:2:"15";i:2;s:4:"2018";i:3;s:1:"4";i:4;s:2:"00";i:5;s:2:"PM";}s:10:"first_name";s:4:"Paul";s:9:"last_name";s:5:"Sapio";s:13:"daytime_phone";s:10:"4803324094";s:13:"email_address";s:20:"paulrsapio@gmail.com";s:13:"training_type";s:7:"MEDICAL";s:19:"program_of_interest";s:19:"Pharmacy Technician";s:21:"educationalbackground";s:12:"Some College";s:7:"chatter";s:4:"Adam";s:8:"comments";s:4:"test";s:9:"ad_source";s:4:"Chat";s:13:"vendor_source";s:9:"Chatdrive";s:3:"_ga";s:27:"GA1.2.1095048055.1520618842";s:5:"__qca";s:27:"P0-1360557608-1520618842179";s:23:"__lc_visitor_id_8301891";s:22:"S1520618843.431c384db1";s:6:"__lotr";s:23:"https://www.google.com/";s:5:"_lo_u";s:1:"1";s:6:"__lotl";s:22:"https://www.asher.edu/";s:4:"_gid";s:27:"GA1.2.1163280825.15211! 28331";s:9:"PHPSESSID";s:26:"oj43a8laru7ih04neg8nocnma7";s:13:"lo_session_in";s:1:"1";s:5:"_lo_v";s:1:"9";}

  • Profile Image
    Kevin_G
    Answered on March 15, 2018 at 02:56 PM

    I have been testing this and I can see what you're reporting, if the field name is in uppercase it should remain like that when sending the POST data. 

    I  will forward this thread to our second level so our developers can have a look on this, we will keep you updated via this thread. 

    Thanks. 

  • Profile Image
    paulsapio
    Answered on March 16, 2018 at 12:33 AM

    Hello any update on this?

  • Profile Image
    Nik_C
    Answered on March 16, 2018 at 07:06 AM

    I'm afraid that the issue is still being worked on.

    We will inform you as soon as the issue is resolved.

    Thank you!

  • Profile Image
    paulsapio
    Answered on March 19, 2018 at 08:49 PM

    Any update please? 

  • Profile Image
    tina
    Answered on March 20, 2018 at 01:44 AM

    Your thread has been assigned to our developer already and it's flagged as important. As promised, you will be notified on this same thread when there's an update.

  • Profile Image
    paulsapio
    Answered on March 26, 2018 at 10:36 AM

    6 days and no update? 

  • Profile Image
    Nik_C
    Answered on March 26, 2018 at 12:05 PM

    We're sorry for the delay.

    The issue is still being worked on by our colleagues from the backend team.

    We'll inform you as soon as the issue is resolved.

    Thank you!

  • Profile Image
    paulsapio
    Answered on April 04, 2018 at 09:04 PM

    any update? 

  • Profile Image
    Jim_R
    Answered on April 04, 2018 at 10:22 PM

    Please accept our apologies. Like you, we're also waiting for an update. Once a thread is escalated and assigned to a developer, the developer can either update us internally, or update you straight away on this same thread.

    Let me leave a note to the assigned developer and ask for another update on your behalf. Thanks in advance for your patience and cooperation.

  • Profile Image
    paulsapio
    Answered on April 12, 2018 at 02:54 PM

    Update please, this is going on like 3 weeks. 

  • Profile Image
    Nik_C
    Answered on April 12, 2018 at 03:41 PM

    I'm sorry but we don't have any updates at this time.

    I'll follow up with developer assigned for a possible information regarding the issue.

    Thank you for your patience.


  • Profile Image
    paulsapio
    Answered on April 18, 2018 at 02:49 PM

    This is going on for over a month, and you guys have giving me the same answer for a month. This is starting to get a little silly. 

  • Profile Image
    Jim_R
    Answered on April 18, 2018 at 03:27 PM

    I can relate to your frustration. We are leaving messages to the developer assigned to your thread whenever you ask for an update. I'll personally get in touch with him again and hopefully, we'll get an update or any news about this issue.

  • Profile Image
    paulsapio
    Answered on April 24, 2018 at 11:46 AM

    Any word Jim? 

  • Profile Image
    Nik_C
    Answered on April 24, 2018 at 12:31 PM

    I followed up again with our higher support for any update regarding this ticket.

    We will get back to you as soon as possible.

    We're very sorry for the delay.

    Thank you!

  • Profile Image
    Denis
    Answered on April 25, 2018 at 04:29 AM

    Hello,

    Sorry for the inconveniences caused. I am sorry to say that our system handles question names as lower case. To keep backward compatibility we cannot update this on our side. But you can handle this on your backend. If you can share your backend information like which programming language you are using, we will be happy help you with this problem. 


    Regards.

  • Profile Image
    paulsapio
    Answered on April 26, 2018 at 12:06 AM

    Denis, 

    We are trying to pass post data though to another system where the fields have to match up exactly. There is pretty common when having to past post data, I do not understand what being able to pass uppercase or lowercase has anything to do with backward compatibility? 

  • Profile Image
    Denis
    Answered on May 15, 2018 at 03:51 AM

    Hello,

    Our users that are currently using this feature might be damaged by this change. That is why we can not update this. Again sorry for the inconveniences. 


    Regards.