ANCHOR_TAB_STRING_NOT_FOUND

@Michael.Rave I just tried removing all the flattening but still ran into the same issue. I will test further to make sure that it’s still getting flattened somehow. in the meantime, i got around the issue by adding the anchor string as text to the pdf itself instead of generating it dynamically. i will have to make additional changes because i designed it to print the anchor strings if the fields were mapped to the pdf, but now we’ll need to handle that another way. if you find any other solutions, please let me know because i would’ve really liked to have generated the anchor strings dynamically based on certain conditions. thanks!

I am also experiencing a similar issue. I’m using the C# SDK. The baffling thing is that I can see the anchor strings on documents sent for signing.  If it’s a base64 issue, what options should I explore. In the example code they first create a template with the base64 encoded document before creating the envelope which seems to work. Creating a template feels like an overkill since all the documents are unique.

I got it to work with a docx document. Seems like with pdf, once you base64 encode it, it does not work

@vinarah it seems if you are printing the anchor strings in a text box field on the pdf, then it doesn’t work. i had to edit the pdf by adding text (without adding a text box) directly onto the pdf. sucks because i designed everything to work by dynamically printing the anchor strings in the text boxes if the anchor strings were mapped. then we would look for these fields being mapped to determine if it’s a docusign-able document. i wasn’t able to find a solution so i finally gave up and completely redesigned everything. what’s strange is that even though the anchor string is printed on the pdf, docusign wasn’t picking it up. if you find a solution, please let me know because i would love for this to work as i had originally designed it.