What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.


  • Profile Image

    SalesForce Integration: Apostrophes sent from a Long Text Entry field are being replaced by HTML code.

    Asked by mashape on June 20, 2017 at 02:11 PM

    Hello Jotform Support,

    I'm getting a funny error message on my jotform submissions whenever someone uses an apostrophe.  

    Example, this came from a lead that was created today:  plaquet.bart@platinion.com

     

    If you scroll down to the "How Can We Help You" field, you will see the following.  In jotform, the Don't appears correct, however, when it comes thru to Sfdc, the sentence looks like:   Don't hesitate to contact me for more info.

    Have you had other issues like this happen?  Any recommendations on solving?

    Thank you,

    Maria

    Screenshot
  • Profile Image
    JotForm Support

    Answered by BDAVID on June 20, 2017 at 03:42 PM

    I have been able to reproduce the same issue. It appears like apostrophes are not being sent correctly to SalesForce, as they get replaced by ':

    But this only happens if it comes from a Long Text Entry field. I did a second condition, but this time using a Short Text Entry field, and it worked fin:

    I have forwarded this to our back-end team. You will be notified via this thread when the issue gets fixed.

  • Profile Image

    Answered by mashape on June 20, 2017 at 05:20 PM

    Thank you!

  • Profile Image
    JotForm Support

    Answered by NeilVicente on June 22, 2017 at 08:22 AM

    Hi there,

    This is now fixed.

    Cheers!