Signature and date fields not working in forms
Copy link to clipboard
Copied
I have a form I am creating which has a number of text fields, a number of radio buttons for mulitple choice questions and a few signature and date components. everything seems to be working fine except for the e-signature and date fields. Once I save the form and send it to a collegue, they open it in preview for mac(as they don't have adobe) they can run through the text fields just fine, when the come to the signature field it shows a box you can move about the pdf but not do anything else and the date field acts the same a text field. I'm simply looking to create a form that customers who are not very technically competant can easily fill in and sign.
Copy link to clipboard
Copied
in the future, to find the best place to post your message, use the list here, https://community.adobe.com/
p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post (like this one has already been moved) if it helps you get responses.
<"moved from using the community">
Copy link to clipboard
Copied
Thank you for reaching out.
As mentioned, the issue occurs only with the signature and date fields. Please let us know how the PDF form was created.
Share the sample PDF on which the issue occurs. It would be helpful if you could share the screen recording of how it appears on the colleague's end.
Share the application and OS version used by your colleague. Also, confirm if the issue occurs with all forms or some particular forms.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Thanks Meenaksi for your reply,
Please see attached pdf and screen recording as per your response.
As you can see from the recording there are a number of text fields which are fine, however the signature field you can't do anything with and the date field is acting as a text field.
The form was originally created in as a word document. I converted it to a pdf and followed the instrctions from another thread regarding creating a form. I opend the document in adobe and selected creatre a form, I unchecked the box for creating a fillable form and turned off autodetect as highlighted in the other form.
I used Adobe Pro version 2024.002.20687
My colleague opened the form in Preview for Mac.
Copy link to clipboard
Copied
Don't use Apple Preview. Open the docment in Acrobat Reader or Adobe Acrobat.
Copy link to clipboard
Copied
Yes, but what i am lookiong for is an easily filled in form for customers that are not in any way techincally savy, I assumed that once the fields are correct that anyone opening the document, no matter what program they use to view the pdf, that it was behave in the same way making it a straightforward process to fill in. what i have here is a pdf that appears can only be opened with adobe (which most of our customers wouldn't have or know how to use) for it to behave in the manner that i would hope it would?
Copy link to clipboard
Copied
You assume wrong, I'm afraid. Unfortunately, there are many sub-par PDF viewers out there that don't handle form fields correctly. Even more unfortunately, Adobe Reader has now joined that list with the bugs it has in the latest update. Let's hope Adobe fixes them soon so it can return to be the industry standard it was until now. But you can't assume form fields will work everywhere, is the bottom line.
Copy link to clipboard
Copied
great, would it be better to post the form to our webpage then and have customers fill it in there?
Copy link to clipboard
Copied
As a PDF file? That won't solve anything, since you can't control how the file is going to be viewed by the users.
Copy link to clipboard
Copied
adding similar. Actually what i am seeing now with Adobe sign and Macs, laptop or iphone is that conditional rendering doesn't work. if i open doc with conditional fields in Preview on laptop or on iphone with native mac email app, all fields will show and the conditions don't work... Waiting for support to let me know if this is a known issue and if there's a workaround

