Skip to main content
Participant
August 25, 2022
Question

Adobe detecting fields that should not be a field

  • August 25, 2022
  • 2 replies
  • 191 views

Hi everyone - I have an agreement that is first prepared in Word and then converted to PDF. I am hoping to use the PDF for the other person to sign. However, when I prepare the form, it is detecting random fields (withn the agreement, at the top of the page, etc in random spots). 

 

It does detect the fields I want (name, address, signature, date etc) but I am wondering how to correct the incorrect fields? I have edited the word doc to remove any spaces as I initially thought that was the issue but if there's any other advice or tips I would love to know 🙂 

This topic has been closed for replies.

2 replies

try67
Community Expert
Community Expert
August 25, 2022

As mentioned, the results of the fields detection wizard will never be perfect, and we don't really have access to how it works or why it does what it does, nor can we modify how it works. We can only guess based on past experiences and try to adjust ourselves accordingly.

 

However, there is a more consistent way of doing it, especially if this is a file you've created.

A script can be used to detect certain characters (or character sequences) and add a form field on top of them, with pretty much 100% accuracy. I've developed two such (paid-for) tools, one for creating check-boxes and radio-buttons based off of Wingdings characters, and another to create text fields based off of sequences of underscores.

If you think these tools can help with your situation you can find them here:

https://www.try67.com/tool/acrobat-reader-convert-wingdings-characters-to-check-boxes-or-radio-buttons

https://www.try67.com/tool/acrobat-reader-convert-underscores-to-text-fields

 

Legend
August 25, 2022

Detecting fields is wild guesswork (how can it really know), so it's only the first stage. If it helps you, detect fields. But most people don't. Then delete any fields you don't need, and add the ones you don't. You're going to need to check and set the name for each field anyway, detecting fields isn't the great timesaver it first seems.