Skip to main content
Participant
January 17, 2024
Question

text tags not working in new request e-signature experience

  • January 17, 2024
  • 6 replies
  • 3179 views

Adobe Acrobat Pro just changed for me to the new Request e-signatures experience and all the text tags I have put into my templates are no longer being recognized and turned into fields automatically, even when I switch back to the legacy version. Has anyone found a way around deleting all the tags an manually inputting all of the fields? My templates are created/modified in Google Docs before turned into PDFs because that is the workflow that works for my business, so I can't save it as an Adobe template and make my edits there. It will be a lot of extra work for me if the tags are no longer usable.

6 replies

nvrlift
Participant
March 2, 2024

Have the same issue here.  Old version works great, new version does not.  The text tags just don't work when you send out for signature.  Revert to old version and all is great.  New version lets the recipient edit all the fields (which they should not be able to).  So frustrating and so many hours wasted trying to figure it out.

 

How 

Adobe Employee
March 2, 2024

Hi,

Sorry to hear that its not working for you. There is a setting under "Adobe Online Services" that lets users revert to legacy request signature experience. However, we would greatly appreciate it if you could provide us with a file that has text tags so that we can check the issue on our side. Also, there is no change in the behavior of recipients, so recipients should still be able to edit fields that they are intended to. If you can help provide a PDF for video with issue highlighted then we'll try to fix it.

Participant
March 13, 2024

Thank you for informing the community about the option to revert to the legacy request signature experience. That worked.
It would've been helpful to all if you announced this HUGE change in Sign to your customers so we could prepare for it and also made the option to revert more visible (I wasted much time manually deleting tags today from an urgent proposal so I could get it out).

Participant
February 16, 2024

Hi there!

For me text tags work when using a Word document and the Adobe Sign plugin. But when I create a pdf first and use the signature feature from Acrobat the text tags are not recognized.

 

Switching back to the old UI did solve the issue. Thanks for the tip!

JR Boulay
Community Expert
Community Expert
January 25, 2024

You must revert to the Classic UI: https://community.adobe.com/t5/acrobat-discussions/acrobat-2023-how-to-revert-to-classic-gui-user-interface/td-p/14052807
Consider the new Acrobat as a beta version, many features are missing or half-implemented.

Acrobate du PDF, InDesigner et Photoshopographe
Participant
January 25, 2024

I was able to completely uninstall Acrobat and when I reinstalled it, the old version was restored. I don't know how long it will last before Adobe will force me back to their new version, but anyone else reading this thread might want to give it a try.

Participant
January 25, 2024

Scratch that, it already converted me back to the new version that doesn't recognize text tags. Hopefully someone from Adobe can give us some insight into what is going on.

Participant
January 22, 2024

I’ve encountered the same issue - all of the text tags are no longer being recognized and turned into fields automatically. I’ve run a simple test with the text tags by copying/pasting the text tags straight from the official Adobe documentation (https://helpx.adobe.com/sign/using/text-tag.html), but unfortunately, they don’t seem to be working as expected either.

It would be great if anyone could provide some guidance or a potential solution to this problem.

Thank you in advance for your help!

Participant
January 18, 2024

Is there a way to revert the E-signatures back to the old look? But yes it seems this update to E-Signature is causing some issue with the cell format as well when folks conver a word file to pdf. Basically it cuts out the date next to the signature now insteall of showing 2024 its 202... in the date field