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.
Unwanted 0D and 0A code inserted in field inputAsked by marrese on August 29, 2013 at 04:53 AM
Hi, we satisfactory use Jotform since 3 years.
In a complex form we are experiencing unwanted 0D or 0A crt in long field.
the field is set to 120 size, while max input is 90.
The form is at this url
being the field #input_52
JotForm 0D and 0A Unicode characters unwanted 0D 0A CRLF
I believe you're referring to the Carriage Return (0D) and Linefeed (0A) Unicode characters. But is there any reason why you did not want to use the standard Address field (Figure 1) instead of using separate text boxes for the address? If it's a matter of not wanting to display certain inputs of that field, they can be hidden by unchecking the boxes in the Fields tool (Figure 2).
(The "Provincia" dropdown could always be retained as a separate field.)
Would this solve the problem?
thanks for the prompt reply.
Unfortunately the standard address field cannot be adopted in this time because edited field is mailed to ZOHO Creator application.
Actually the form works fine, but sometime there are 0D or 0A chars in the string.
As ZOHO use this string to recall the same form with prepolulated fields, it became apparent that something doesn't work properly.
Any other suggestion or workaround to avoid the inconvenience?
Thanks & Best regs
I think these characters are being caused when some users hit [Return] (Enter) while entering their address. The best workaround I can currently come up with is to attach a "Hover Text" note to the field asking users not to press that button but use their mouse instead.
Hopefully, my colleagues can devise a better solution.