Hello @Rameshwari,

Thank you for reaching out here in the DocuSign Community.

I apologize for the inconvenience that this might cause you, I know the importance of showing the fields in an envelope as needed; I understand that you are having issues with the anchor string using Power Automate.

To confirm, are you using DocuSign for Microsoft Power Automate integration?

If yes, To configure a document for adding tabs, follow these steps: 1. Create a Document Custom Field in DocuSign to define the AutoPlace text. 2. Add the AutoPlace Text to the document in an editor. 3. In the Power Automate flow, use the DocuSign action "Add tabs for a recipient" and enter the AutoPlace Text in the tabs anchor string field.

More detailed information at Configure a Document for Adding Tabs

Note: Some advanced features and options are supported only in specific DocuSign plans. Your account plan might not support some options discussed in this help topic. Contact your account administrator for more information about which options are available for your account. Or, visit our Plans and Pricing web page for more details on the features included with your plan. Compare eSignature plans & pricing.

Hi @christopher.alpizar,

I am having a similar issue within Power Automate.  My trigger is when a PDF is uploaded to a SharePoint library, creates the DocuSign envelope and first sends to the Project Manager for signature, then to their Manager for signature with date signed/approved.

I’ve read on the DocuSign Support page that the AutoPlace Text should be as follows:
Signature: \s\
Date Signed: \d\ 

So, I assume for my flow they should be:

PM signature:  \s1\
Manager signature:  \s2\
Date Signed:  \ds2\

I’ve entered the same text inside the Anchor Tab String fields.  Are these incorrect? 
I’ve tried without the slashes, frontwards, backwards, and still receive the same error, “The specified Anchor Tab string was not found in the document.” 

We have a Business Pro account.  
 

Hello @RebekahG,

Thank you for reaching out here in the DocuSign Community.

I apologize for the inconvenience that this might cause you, to confirm both the string in the custom field and the one in the document are the same one? Normally the strings are case-sensitive.

Thank you for your response @christopher.alpizar .

Yes, all three strings match.  The custom fields, in the document, and in the Flow.

Hello @RebekahG,

Thank you for reaching back, would it be possible for you to provide an example of the PDF that you are using? and also please confirm if the issue persists with a Word format document.

I was wondering the same thing @christopher.alpizar . 
We prefer a fillable PDF, I’ve used AI Builder to transfer all of the fields into a SharePoint list within this same flow.  The last portion is getting it signed and approved.  

I seem to remember running into other issues using a Word file.
Please see attached PDF.

Hello @RebekahG,

Thank you for reaching out here in the DocuSign Community.

I apologize for the inconvenience that this might cause you, I got more information on your issue, and after further investigation, it seems that based on your document you are not embedding the anchor strings correctly. The PDF that was provided shows that it was created with Adobe Form fields and then put the anchor strings as values inside those fields, that's not what the DocuSign system is looking for, this will work if you were uploading this document in the DocuSign Web App because, during the add fields section of the envelope creation, the system will prompt the user to either:

Create new DocuSign fields and keep the pre-filled values.

Or just flatten the fields, or delete the Adobe form fields.

It is expected that if you select the option to flatten the Adobe Form Fields, it will turn into real text on the document, then you can use the anchor tags.

The issue is that when you upload a document to an envelope via Power Automate, you don't get the opportunity to select the option mentioned earlier in this post in the DocuSign Web App.

I'm guessing it just drops the Adobe tags altogether, if you need to keep all the Adobe fields as your users might be filling out these forms in Adobe before uploading them into SharePoint, that's fine. but we cannot confirm if that data will be preserved when uploaded via Power Automate.

To make anchor tags work, you will need to embed them in the pdf as normal text, not form field values. 

Best regards,

Christopher | DocuSign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

@christopher.alpizar 

Hi Christopher,

Thank you for the response.  I’ve removed the form fields from the signature lines and just left the white anchor tags.  However, the flow still fails with the same error that the tags aren’t found within the document.  

Am I understanding correctly, that flattening the PDF before uploading it to the envelope might work?  Or will the tags be dropped regardless, when using the action to upload the file to an envelope via Power Automate?

Thank you!
   

Hi @RebekahG,

I hope you are doing well.

Yes, when the PDF is flattened it will remove any unnecessary metadata in the PDF. This should convert the text information into plain text.

Let us know if you need further assistance with this.

Best regards,

Christopher | DocuSign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Hi @RebekahG,

I hope you are doing well.

I would like to confirm if you were able to solve your issue by utilizing the solution that was suggested or if the information that was provided was useful.

If so, please mark it as the best answer by clicking “Select as Best” to make it easier for other users to find.

Otherwise, feel free to let me know and I will gladly help you address the situation as soon as possible.

Best regards,

Christopher | DocuSign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Hi @christopher.alpizar 

I have flattened the PDF but still receive the same error. “The specified Anchor tab string was not found in the document.  Anchor Tab String “\s1\” not found.”

I have seen articles where the anchor string is used with forward slashes but also with backwards slashes.  Does this matter?  Also, here’s a screenshot of my failed Flow where the output for “tabs” displays 4 forward slashes but my document only consists of two.  Just find this odd but not sure if it’s causing the error.

Hi @RebekahG,

I hope you are doing well.

At this point, I recommend opening a case with DocuSign Support and having a specialist review this in a screen-sharing session.

To open a support case with DocuSign, log into the DocuSign Support Center using your credentials. Select your profile image, then click on "Manage Cases" and "New Case". Choose a category and sub-category for your issue, complete the case form, and submit the case. Case statuses include Open, My Action Required, Pending, and Closed. If your case is closed but the issue persists, open a new case and include the case number of the closed case in your comment.

How do I open a case in the DocuSign Support Center?

Best regards,

Christopher | DocuSign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Will do.  Thank you so much for your help thus far.

Hi, did they managed to help you? I’ve got the same problem